In the setup we use, we look at Issue Types from a slightly different perspective than you might be used from if you come from an Agile setup. Rather than working with a Story as issue type, which is the common practice in Agile where you do exploratory work based on ideas and concepts, we work from the assumption that all issues in Jira Software are work orders. For this reason, we do not use the Story issue type, but rather have defined issue types based on the actual work that is to be done. This may seem strange if you are used to working with Stories, but from a logical perspective this makes sense as we divide between documentation and work activities. Since there is also no 1-1 relation between any of the AOR's, it makes sense to ensure that this is represented also in the issue types where we define the work. We still have issue types that can be used for ideation and exploratory work, we just remove Story as it is often interchangeable with a requirement and for this reason often abused in many setups. Since we also want to periodically delete issues to keep the system clean, we want to avoid ending up in a situation where we can not do that because important documentation has ended up in work orders in Jira issues. In order to provide separation of work, we also want to make sure that actual realization of requirements are separate from other types of work. This includes adding issue types for ideation, design, technical debt and of course investigations as none of those are related to development and they still should be possible to track and optimize from a work perspective. The Issue Types: Story (deprecated) Epic Incident Defect Frontend Development Backend Development Build & Configure Design Investigation Task The Sub-tasks: Sub-Task Defect Sub-Task
