I have run into this situation where I noticed that if I do a search on the records, the search results page will yield e.g.
Incident 1 Status: Acknowledged, Resolution: Unresolved
But, if I select Incident 1 and am on the details page it has e.g.
Incident 1 Status: Closed, Resolution: Fixed
There have been many variations to what the values are on both sides search results/detail page and so I really need to know where the values are being pulled from in the database for both areas in regards to the Status and Resolution.
Don't bother asking me why it does it all I know is that the system is old and has been grossly coded to make things work where obviously it is not working correctly so I need to gather metrics on the data where things are not in sync.
Community moderators have prevented the ability to post new answers.
The discrepancy between the Search result and the Actual issue is almost always down to a damaged index record. Try re-indexing the project the issue is in and
If it helps explain it, no SQL database can possibly keep up with Jira's load that could be imposed by searching, so JIRA keeps a local index for searching. When you look at an individual issue, you are looking at the data from the database. But search uses the index, so if the index is corrupt, the search comes back wrong.
If a re-index fixes it, then you probably want to investigate why it broke. It can happen on system crashes, but 99% of the time, it's because of a broken post-function in the workflow, or a dodgy plugin hacking the data. In this case, it's probably something on the workflow transition from "acknowledged" to "closed"
But there has to be two locations where this is stored right?
How else can the same incident have 2 sets of answers for 1 record?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
IT doesn't. Status is one thing, resolution is another. Position on your board (i.e. "done") is actually a third, although it is backed by the status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not sure about JIRA 4 but try looking at the table jiraissue (issuestatus and resolution).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.