Hi guys, I'm querying the REST API for feature groups data with the following URL:
There are feature groups that contains data in the Jira Web UI as shows the following image, but those transitions in some cases are not present within the response of the feature group (customfield_10201 is null)
This value is received for only in a few feature groups' response:
I need to get the transitions data from the response for every feature group.
Sorry, it took me a while to work out what "feature groups" were and realise they're not really important here. They are just something (a custom field, issue type or label, etc) that group together the issues you are interested in.
Now, for any issue, you are actually looking at two things here.
The picture you give us is a screenshot of a "transition history tab". This is a display built by some code that looks back over the full history of an issue, pulls out the transitions and works out the time spent in each status and the number of executions.
The string of numbers, underscores and stars is the "time in status" field, from another (system) add-on. It's gathering data for the time in status gadget.
I suspect you'll need to read and parse the history for yourself to do your reporting over REST.
Hi Nic, maybe I wasn't clear enough describing the problem. Yes, I need to read and parse the history to my report over REST, actually that is what I'm doing for some of the "time in status", having that context in mind the question is:
Why I don't get the "time in status" value for every Issues REST's responses?
Some issues may not have any data for it - new issues for example, the "time in status" is not calculated because it's changing constantly until they move to a new status (created time is a fixed point, but "now" isn't). The field might also not be valid for the issues too.
I'd be looking in the history for this stuff anyway.
You are guessing that the time in status field is gathering information for you. It's not, it's gathering it for the time in status gadget, which may not have the same data requirements that you do. You can't rely on this field because you don't really know what it is doing.
You will need to read the issue history.
Right, but it still does not answer my question about why the "customfield_10201" does not have value in some "Issues Fields" that share similar status transitions.
It's not ok to have to process the data from history's response to get data that came already processed for some Issues in "custom field 10201".
Because the gadget does not need the data, the code decides not to put anything in there. As I said several times, this field is being calculated (or not) for a report, not for you.
You need the full set without that code doing things you don't need to know about, so you'll have to read the history.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs