-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Rationale
Messages can be posted immediately to share knowledge, informations to a group or to a network.
❓Then, What is the problem?
Currently, it is not possible to schedule a post while this is allowed for news publishing for example. In addition to this, users have reported this more and more about this missing feature.
Indeed, as it is possible when sending e-mails or when using other social network (facebook for example), it is expected to schedule a post for a later date in order to plan publishing. In addition, this would be interesting to not make noise while others are not connected.
🎯 What is the goal?
For posts (incl. kudos), have the ability to schedule post and then to manage scheduled posts.
1. Functional Requirements
Top User Stories
Schedule
- When creating a post, then you can decide to post it immediately or to schedule it
- When scheduling it, then the default schedule is the day after at 8am
- It is possible to select a date and/or a hour
Manage
- Once scheduled, it is possible to access scheduled post from the feed filters
- For scheduled post, the options are only 'edit' and 'cancel'
- 'Cancel' cancel the schedule and remove the post
- 'Edit' opens the composer with option to post immediately or to change the schedule
- Space admin (incl. space coordinators), space publishers and space content writers must have access to scheduled post of other admins, publishers, writers.
- When doing so, then both schedule & authoring are updated
Other business rules
- Notifications are sent only once the post is sent
- The unified search excludes scheduled post
Impacts
Gamification
N/A
Notifications
Notifications must be sent only once the post is sent
Analytics
N/A
Unified Search
Scheduled posts must be excluded from the search
2. Technical Requirements
Expected Volume & Performance
Security
Extensibility
Configurability
Upgradability
Existing Features
Feature Flags
| Property Name | Default Value | Target Audience | Functional Behaviour |
|---|---|---|---|
Other Non Functional Requirements
3. Impacts
Documentation
Training
4. Software Architecture
Security
Access
- GUI
- API
Services & processing
- Ex: Scheduled Jobs
Data and persistence
- Macro data model
- Persistence layer
- Use of caches
Clustering
Multitenancy
Integrations
Migration strategy
5. Annexes
- Reasoning that explain the technical choices
- Impacts
- References