/
What’s New? · Oct

What’s New? · Oct

12.png

Approval state is now in your Jira data🔎

Five new custom fields carry approval information into Jira itself: status, progress, percentage, and who still has to decide.

Frame 213 (2).png
They are read-only, so they report what is happening rather than let anyone change it.

Field

Shows

Field

Shows

Approval Status

In progress, Approved, Rejected, or Incomplete (the deadline passed with no decision). Empty when the work item has no approvals.

Approval Progress

Step: x/y, the same format as the approvals list

Approval Percentage

A number from 0 to 100, so you can compare (>= 50), sort, and aggregate

Pending Approvers

Who is awaiting a decision on the active steps. A user field, so = currentUser() works.

Pending Approver Groups & Emails

The groups and external approver emails still to decide

Because they are ordinary Jira fields, they work everywhere ordinary fields work. Put them on board cards, add them as columns, sort by them, write JQL against them. Finding every work item stuck waiting on the same person is now a filter you can save.

 

A Overview that is already set up 📊

Global and space admins get a default overview with the key approval metrics, a list of items needing attention, and charts for workload, cycle time, and upcoming deadlines.

view.gif
There is nothing to configure. Open it and it is there.

 

Approvals that work on a phone 📱

Approvals arrive when you are not at your desk, which is exactly when the interface used to make you work for it.

Row actions now collapse into a menu on touch devices, layouts stack instead of running off the side of the screen, and dialogs keep their buttons where you can reach them. Deciding something from a phone is no longer a test of patience.

 

Stop emailing people who cannot act yet 🔕

Watchers were notified when an approval started and again on every step decision, all under one setting. In a sequential approval that tells everyone on day one, including whoever is not needed until step four. The only way to stop it was to silence the lot.

Those are now two separate switches. Turn off the start notification and keep the step decisions, or the other way round, whichever matches how your team actually works.

image-20260930-160620.png

You can go finer too. A single approval definition can opt out of the start notification on its own, and an individual step can opt out of its decision notification, both under a Watcher notifications section in their settings. Turning an event back on globally restores whatever you had set there, so nothing is lost while it is off.

What else changed? 🛠️

  • Added the Block transition until rejection workflow condition. Rejections now get the same control approvals already had.

  • Grouped the global settings into collapsible sections, so you can see what is enabled at a glance.

  • Updated status wording so comments and notification emails read Approved, Rejected, Waiting, or In progress.

Comments