setting up the scrum process in Jira Datacenter

[Acio Manuel Francisco Nhacutou]

I am setting up the scrum process in Jira Datacenter and would like to request support in implementing the following requirements in our scrum process in Jira. 1. Implement release approval. I have not been able to identify a way to do this in Jira. 2. Implement a view/dashboard that allows me to view all releases from all projects filtered by date (start date or release date). I have tried but have not been able to manipulate (add) the quick filters for releases. 3. I would like to add notes to releases. We are unable to edit the release notes. 4. How to record progress in the development of issues. Is it possible to create multiple tasks for an issue and record the progress (time spent) on each task that makes up the issue? 5. Implement custom fields at the release and sprint level. I need to include additional information in these 2 items

[Iryna Menzheha_SaaSJet]

Hi @Acio Manuel Francisco Nhacutou  👋 Welcome to the Community!

It’s great that you’re configuring the Scrum process in Jira Data Center — and you’ve raised some really good and specific questions. Let me walk you through each one:

---

Implement Release Approval

Jira doesn’t have a native "release approval" process, but here are two ways to achieve this:

• Option A: Use a Custom Workflow Status
  Create a status like "Ready for Release" in your workflow and ensure issues can’t be moved to "Released" until they pass through this status and get approval (via comment, field, or assigned reviewer).

• Option B: Use a Custom Field + Automation
  Add a custom checkbox field like “Approved for Release”, then use Jira Automation (or a validator) to prevent the version from being released until this is checked.

For even more control, some teams use apps like ScriptRunner or JMWE (Jira Misc Workflow Extensions) to add approval logic.

---

Record Progress in Development of Issues

Yes! You can break a single issue (like a story or epic) into multiple sub-tasks and log work individually for each.

✅ Here's how:

• Create sub-tasks under the parent issue (e.g., "Code", "Test", "Docs")

• Team members can log time spent on each sub-task

• Progress will roll up to the parent issue if you configure Time Tracking correctly.

⏱ For better time tracking insights (e.g., Time in Status, Time in Progress), Time in Status app can provide detailed reports.

---

Time in Status app developed by my team.

Let me know if you’d like help setting up any of the above or need links to specific apps! 

[Trudy Claspill]

Hello @Acio Manuel Francisco Nhacutou 

I don't have answers for all your question yet, but here are a few answers.

4. How to record progress in the development of issues. Is it possible to create multiple tasks for an issue and record the progress (time spent) on each task that makes up the issue?

The above can be accomplished using the Sub-task issue type. Sub-tasks are children of other issue types (i.e. Story, Bug, Task). Sub-tasks can't exist independently of being a child of another issue. When you use time estimation and log time against a Sub-task you can elect to show that information summarized on the parent issue.

5. Implement custom fields at the release and sprint level. I need to include additional information in these 2 items

This is not possible with native functionality. Are you willing to consider getting a third party plugin to meet those requirements?

[Acio Manuel Francisco Nhacutou]

Yes, I am interested.
What is the procedure to get the plugin? If there is documentation, I would appreciate it if you could share it.