-
Suggestion
-
Resolution: Low Engagement
-
None
-
0
-
2
-
Problem Definition
Currently, there is no documentation on how does JIRA Software reports are being generated from backend or what are the conditions that have to be met for issues to be included in the reports.
Suggested Solution
Have a section in JIRA Software Reporting explaining on how does the Reports are being generated.
Notes
For example, Release Burndown report is being generated:
- Take all issues which are displayed on the board and gather all sprints from them.
- Take all sprints which belong to this board.
- Let's union these two sets.
This is how all the Sprints are being gathered in this report at the backend.
- relates to
-
JRASERVER-28748 Project Imports should include relevant Active Objects data
- Closed
-
JRASERVER-65270 Project import to allow JIRA Software Board mapping
- Gathering Interest
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center