In Jira, when there are split items (story->epics, epics->tasks), reviewing the split items requires a lot of work and juggling between multiple pages in Jira. The suggestion is to create a document with all the planned items to be split on the parent entity (a document with all the epics accessible from the story page, a document of the tasks accessible from the epic page), and only when the doc is approved, create all the child entities based on the doc. This will make the review process much simpler.
Open question - how to handle the files?
- Attachments in Jira
- Keep them in GitHub and put a link in Jira (requires handling commits before we planned to open the branch)
- A combination, start with attachment, but eventually add to github for better auditing after the process is completed
- Other?
In Jira, when there are split items (story->epics, epics->tasks), reviewing the split items requires a lot of work and juggling between multiple pages in Jira. The suggestion is to create a document with all the planned items to be split on the parent entity (a document with all the epics accessible from the story page, a document of the tasks accessible from the epic page), and only when the doc is approved, create all the child entities based on the doc. This will make the review process much simpler.
Open question - how to handle the files?