Great question and one that could probably spark a lot of discussion as to what's best. A lot of the answers really depend on what you want to get out of your devops.
My initial thought is that your stack of Jira+Bitbucket+Confluence is not end-to-end in terms of DevOps products that Atlassian has.
I think end-to-end using full range of Atlassian's tools would look something like this:
-
Capture ideas in Jira Product Discovery
-
Link ideas to epics in Jira
-
Create branches in Bitbucket
-
Run Pipelines builds and scans
-
Display build results in Compass
-
Document progress and various aspects of your development in Confluence
You can a lot with your Jira+Bitbucket+Confluence stack even without JPD and Compass.
Confluence and Bitbucket integrate with Jira seamlessly, with important part being linking of repositories to Jira.
Jira will serve as your workflow and sprint management platform. The integration you establish with Bitbucket will allow users to see development metadata (commits, prs, branches) and establish a link between jira issues and Bitbucket.
You can set up a lot of devops-related automations in jira to enforce consistency, data integrity and adherence to your processes. For example, you could enforce jira issue transitions and status changes on events like branch created, PR created etc. You can announce important events into Slack or Teams. You could create tasks/sub-tasks or alerts on failed builds or failed deployments.
I personally recommend creating a webhook automation that writes bitbucket comments into Jira.
Your confluence is a knowledge base, so you could do a lot of DevOps related content that is not release or deployment specific. Document things like:
- Project purpose
- Scrum team roles & responsibilities
- Definition of Done
- Definition of Ready
- Field reference - if you have complicated logic for field use (such as drop-down options), you can store the reference in Jira and link to confluence from field description
These documents would be more stable without frequent updates
Your frequently written release-level content could be:
- Yearly / Quarterly planning
- Sprint Planning including goals, risks, capacity, polls, sizing / agile poker discussions
- Retrospectives
- Sprint Reviews / Demos - Loom is another Atlassian tool that's missing and is great for attaching recorded demos
- Release notes
- Embedded Jira reports - this is especially great because jira dashboards don't allow comments/discussions, while Confluence pages do
I can't stress enough the knowledge base use case, so all your documentation should go into Confluence.
I think this sort of scratches the surface. Let me know if you have a more specific question
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.