π οΈ Administratorβs Guide β Issue Delivery Report
π¦ Installation
Issue Delivery Report is a Forge-based Jira Cloud app that installs seamlessly across all issue types.
To install:
Go to Apps β Find new apps
Search for Issue Delivery Report
Click Try it free
Approve the required permissions
The app will automatically appear in the issue view panel of every issue in your Jira instance.
π Permissions
Upon installation, the app requests the following minimal scopes:
read:jira-workβ to fetch issue data and changelogsread:jira-userβ to display the names of users who made status changesstorage:appβ (optional) for future extension (no data is persisted now)
β Make sure these scopes are approved in your siteβs admin settings to ensure full functionality.
β οΈ Note: This app does not write to Jira or modify any issue data. All data processing is read-only, except when exporting.
π§© Configuration
No setup is required. The app works automatically on every issue.
As an admin, you may:
Restrict visibility of the app panel via project-level issue layout configuration
Share the status naming guidelines with your team
Encourage consistent naming for accurate metric calculation
π Updates
Issue Delivery Report is updated automatically via Atlassian Forge.
No manual updates are needed.
π₯ Who Should Use It?
This tool is ideal for:
Scrum Masters β to evaluate blocked or waiting issues
Product Managers β to review delivery timelines and sprint scope
Engineering Managers β to track bottlenecks and efficiency
QA Leads β to understand blocked cycles or delayed testing
Anyone analyzing delivery health of individual issues
π§ͺ Testing Before Production
You can safely install the app in a sandbox environment or test project.
Try it on a few issues to verify status naming conventions and metric accuracy before using it across teams.
π§Ό Uninstalling
To remove Issue Delivery Report:
Go to Apps β Manage Apps
Find Issue Delivery Report
Click Uninstall
π This will not remove any exported data or browser-stored reports.
Since the app doesnβt save data in Jira properties, no cleanup is required after removal.
π§ Admin Tips
β Educate your team about status naming for accurate reporting
β Encourage export usage for retrospectives or external tracking
β Use the βSprint Additionβ indicator to enforce scope discipline
β Share Flow Efficiency insights to drive continuous improvement