Thought I was clever and did a script in Integromat to notify people who still had a status set to a specific kind after two weeks. However it notified someone whose status only changed today. Now I see that even though the previous and current status are different, they're both in the same status category and so the date of status change didn't update. Is there anything that tracks the actual status and not just the status category?
In Jira/JSM, WF statuses are associated with 3 categories (TO DO, IN PROGRESS, and DONE). I am sure you already know that.
By default, when issues move from status to status, you can find the time via the issue's activity log (i.e. Activity tab). At our env, we have created custom fields to store the date/time when an issue moves from one status to another status. However, it depends the need of the users/team - Example: The team wants to track when an issue moves from Open to In Progress status for project A. We customized project A's WF on the appropriate transition via post function to capture the date/time when the above event happened.
The drawback of the above implementation is that this need to be done as per individual project basis.
Your other two options are - 1) develop custom programs to obtain the status transitions date/time looking at issue's history; 2) research in the Marketplace for possible third party add-ons.
Hope this give you some ideas.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
although I have no experience with Integromat I am wondering how the tool's logic might be.
You surely have seen that you can check for issues longer resting in a status than you want them to be by, for example:
status = "Open" AND status CHANGED FROM "In Progress" TO "Open" BEFORE -14d
More information could be found here:
Even with an Automation rule you could use this query - so from my imagination the Integromat solution should work together with a query (like the shown above, please adapt it to your requirements) and it should work.
When you say the status changed the query above covers that. Probably there will be the need to review the Integrator documentation, maybe the solution is not capable for using JQL or needs some further specification how the data should be read.
From a Jira's perspective the requirement is one that is seen daily (nothing special).
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events