The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
I use an automation whose trigger is the change of transition from status A to status B. I want to display the date of change to status B in a field. I had done this :
{{issue.statuscategorychangedate.toDate.jiradate}}
It works very well, it sends me the date of change of status category.
But I want to display the date of the status change. I would like to apply this :
{{issue.statuschangedate.toDate.jiradate}}
Someone would have an idea ?
Best regards,
Estelle
That is not possible with out-of-the-box features; only the status category has built-in tracking which is easily accessible.
Your work-around options are impacted by your cost/easy of use factors:
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
as it is at status change this smart value works : (and avoids code or purchase)
{{issue.updated.jiradate}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please note the updated field will note any changes, not just status transitions. So that field will also change for field edits, comments, etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes of course, it's important to specify it.
I didn't put the automation but it will be clearer :
The trigger is a defined transition. At that moment the smart value with the update date will be applied.
And as the trigger is a defined transition the other updates of the ticket will not trigger the smart value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for explaining, and that is a good work-around!
With automation rules, there is a small-ish chance the updated date/time could still be after the actual transition change...this could happen when automation rule execution is delayed (e.g. automation engine performance in the cloud) and there was another update later (e.g. field edit). Just wanted to note that in case you see differences between your custom field and the issue's history.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Estelle Decanis
To get the status changed date, you can try Time in Status for Jira Cloud from the Atlassian Marketplace. It generates a Status Entrance Date report, that shows the date when an issue has entered each of the statuses. So you'll get an accurate data of status transitions.
You can export data as CSV and XLSX files for further analysis.
It's developed by my team and is free for using up to 10 users. Please, let me know if you have any questions.
Hope it helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.