People who use this screen will be tempted to create massive numbers of Jira issues. We don't recommend creating thousands of issues with it. - Don't create Jira issues in anticipation. Only create issues for tasks that you are going to perform during the next Sprint.
- The value of Requirement Yogi comes from annotating free text. If you keep transforming free text into Jira issues, you are making it painful for you to manage requirements.
- It is much better to link a Jira issue to an entire page, rather than link an issue to every single requirement in it.
- It slows down the instance if you need to update a batch of Jira issues each time you update a Confluence page. We're happy to sell consulting services to diagnose and improve your performance, but it is a painful problem to have, and we've already optimized the product a lot.
This screen is very useful when planning development work, but it won't help if you are trying to maintain the same information in Confluence and Jira. |