The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • How can I create a field in Jira that counts how many times an issue has transitioned to the "Reject

How can I create a field in Jira that counts how many times an issue has transitioned to the "Reject

Juan david
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 7, 2025

Busco la manera de añadir un campo personalizado en Jira (preferiblemente numérico) que se actualice automáticamente cada vez que una incidencia pasa al estado "Rechazada". El objetivo es registrar cuántas veces se ha rechazado una incidencia a lo largo de su ciclo de vida.

¿Es esto posible con Jira Automation o necesitaría un complemento adicional?

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

3 votes
Answer accepted
Bibek_ikuTeam_
Community Champion
April 7, 2025

@Juan david ,

 

Welcome to the community!

 

There is no out-of-the-box feature to avail the same, as a workaround I would suggest exploring automation using custom fields to do so.

 Project Settings > Automation → Create a rule:

  • Trigger: “Issue transitioned”

  • Condition: “To status” equals your target status (e.g., “Reject”)

  • Action: Edit issue → Moved to In Progress Count{{issue.Moved to In Progress Count}} + 1

 

Gracias,

Bibek

 

Juan david
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 7, 2025

Thanks, however I'm now facing a new issue: the automation works correctly the first time and sets the custom field to 1. But when the issue transitions to the "Rejected" status again, the value does not increase it just stays at 1, as if it's not reading the current value of the field.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events