For complex processes, the mapping of initiatives to epics and features to stories can become problematic. The usage of Jira to drive development is hindered by the variable of interference via integration. Some cases may include:
- The desire to prevent interference with epics, which are a special menu in the sprint/backlog area.
- The desire to only have stories that represent correctly written agile user stories that will actually be developed, in concert with a product ownership / management process that may provide less than ideal information.
- The desire to bring the initiatives and epics into Jira, send them through a review process, and only then create things that represent units of work. Note that the usage of status workflows is not completely helpful. While it works, sprint calculations require the closing of an issue, and more work means not closing the issue (or creating some really funky workflows, when the real solution is multiple issues that each carry part of the process).