Objective
Over 25 clients actively use Confluence as part of their daily software development efforts. Mattermost is often used in conjunction with Jira and the two software products are often sold together.
The objective of the Confluence plugin is to:
Plug the “gap” in product support for Atlassian products. We have Jira, there is a community-supported Bitbucket integration, but one of the most popular Atlassian products, Confluence, is not directly supported in Mattermost
Tell a story about the overall “development workflow” and how important toolsets (like Confluence) is well-integrated with Mattermost, building upon “By Developers for Developers”
Make it easier for developers who deal with Confluence to achieve some basic daily tasks and stay on top of changes that are happening in Confluence pages they care about, without opening a browser window.
Have more servers install and activate another plugin (Confluence is a popular request)
Herzum was considering making a connector for Mattermost, but there wasn’t sufficient paying customer demand for them to initiate development.
Success metrics
Goal | Metric |
|---|---|
Make it easier to find confluence documents | Metric: Measure # of times people use search/recents |
Increase customer stickiness | Metric: Measure of Server activations of Confluence plugin |
Increase adoption of Jira plugin (via advertising for Jira plugin) | Metric: Higher rate of activation of both Jira/Confluence servers |
Assumptions
Atlassian using Orgs will tend to use Jira AND confluence
Milestones
Requirements
Requirement | User Story | Importance | Jira Issue | Notes | |
|---|---|---|---|---|---|
| 1 | HIGH | ||||
| 2 |
|
|
|
|
|
User interaction and design
Open Questions
Question | Answer | Date Answered |
|---|---|---|
Out of Scope
Integration with Jira workflows
Creation of content from within Mattermost