Hi everyone,
I hope you’re all doing well.
I’m reaching out for assistance regarding an issue I’m facing with our Jira server (v9.4.14) running on a Linux VM, which is configured with a datacenter license.
We use the "Time to SLA" plugin to track SLAs for suppliers.
The SLA is measured from when an issue is in the "Open" status until it is either "Accepted" or "Rejected" within a 24-hour window. The workflows are set up accordingly.
However, we’ve encountered a problem: sometimes suppliers transition issues from "Open" to "Accept" after the 24-hour deadline, resulting in SLA violations.
If we find the reasons for the delay justified, we update the transition date from "Open" to "Accept" directly in the database using SQL queries and then regenerate the SLA.
This process works well, but we’ve noticed that after updating the transition date, the transition history shows the tag as "unknown," as shown in the attached image.
Currently, we’re only updating the transition dates in the "changegroup" table. What additional steps should we take to ensure that Jira accurately reflects this status in the transition history?
I’d greatly appreciate any suggestions you might have.
Thank you!
In Jira, modifying the database directly is generally not recommended unless it's an absolute last resort. This is because Jira's database structure is complex, and manually modifying records can result in missing or corrupt metadata, as you're experiencing with the "unknown" tag in the transition history.
Hello @Lucas Modzelewski _Lumo_
Thank you for responding back.
Yes, I understand that modifying the data in database directly is very risky but I did know any other alternatives unless you mentioned we can do it via REST API...
If possible, can you please share more details on what APIs in particular exists for the same purpose. I can do my research on this but if it comes from you, then I don;t have to verify and validate the same.
Appreciate your answer. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.