Our Jira instance was originally created by a consulting firm, with the input from our director of product management. I'm trying to locate any documentation/videos for how Jira recommends the use of issue types, specifically for software development teams and perhaps any coinciding automation. We're going through some reorganization and business process flow changes and would like to understand better any best practices we should follow. We now have Premium so would like to take advantage of full capabilities where possible.
For example - We have a Story, which presumably always has the story writeup, development, code review, QA and documentation....should 5 tasks or subtasks auto create whenever a story is created? Or is it best to just have these business steps as statuses and be part of the workflow for the story? A combination of both? Or any other suggestions.
Any insight as to how other software companies have created their issue types/workflows/automation?
Hi @Kim P
Pay attention to the add-on Business Process Manager (BPM) that was developed to create and run a team-friendly business process.
It allows:
Also, there is an opportunity to connect it with Jira Automation to start the process after the selected trigger.
Here is Use Case that can be interesting for you: How Business Process Manager Add-on helps in product releases
If you have any questions, be free to write me. It's developed by my team.
Hope it helps
Regard,
Julia