I gather I can't extract the history chain for Status/Resolution using JQL.
I'm a novice to the programmatic API...
Is it possible to write an API program to query JIRA and extract the history?
The larger goal is to present a report, per issue (grouped by Team), of the elapsed time spent processing completed issues (time from status -> In Progress until -> Accepted).
In a similar vein, to report on the number of issues Accepted, per unit time (e.g. calendar month).
[the workflow goes Submitted, Triaged, Ready for Refinement, Refined, In Progress, Delivered, Accepted, Verified. I can't assume the final resolved time, as it'll change when Verified.]
There is a Python package for interfacing with Jira: https://jira.readthedocs.io/en/master/
I have not used it, so cannot comment on it's robustness.
@Doug Swartz the page you wrote, 'doesn't exit yet', it says? Was there a typo?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
some junk characters ("%A0") on the end of the raw URL.
try https://jira.readthedocs.io/en/master/ which works for me
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
works.
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.
yes - I've use C, C++, C#. Not yet python, but "it doesn't look that hard". Looking for some overall intro and some specifics to get a first bash going.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I wrote yesterday a similar answer. Does this help?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
AH! I see that. So the answer is:
* to get the info needed, you need the fully expanded history
* you can only get that for one issue at a time
* so you need a list of issues, and loop over that.
Is that a feasible load on the server/reasonable time to complete, for a JIRA DB of about 15000 issues?
Is there a Python equivalent rather than direct REST?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Neil Taylro,
all your three points are correct.
There is a server limit of 1000 issues (maxResults) per search result. This limit can be increase by configuration. If you stay within the limit of 1000, it's a piece of cake for Jira.
But you can also create a JQL by create date (monthly), than it is done in chunks.
So long
Thomas
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.