Hi, thanks for that Sam. Is there any JQL I can run to show a table of these items, I'm building a Sprint Summary report which I want to show the effect of my over enthusiastic product owner
There's no JQL that can get it out of the box in JIRA Cloud, I'm afraid.
JQL does support some historical search operators (WAS, CHANGED AFTER, etc), but these only work on certain fields. Unfortunately the Sprint field doesn't support these type of history searches.
WAS
CHANGED AFTER
Of course you can search for JIRA Cloud add-ons which expand search capabilities in various ways, but I'm not sure if you'll find something suitable.
Another option, although not exactly what you want, is the Sprint Health Gadget which shows sprint scope change %.
The Sprint Report has a link next to each kind of completions that retrieves the JQL needed.
You will see that it is not a pretty function, but a csv of issue keys like:
key in (KEY-1,KEY-2,KEY-3)
sprint-report-view-in-issue-navigator.jpg
I find this totally lack of functionality frustrating with the Jira Cloud application. The data is in the system AND Jira does surface it with the * in the sprint report. The fact that we can't get this data via JQL is BS.
Bump @Atlasian
You show us the data in exists in the cloud version, please stop crippling your applications and give us JQL access to it.
Hi , Jira might not support this but you can get the ticket in an issue navigator if you apply a little JQuery magic:
var elements = $("tr.ghx-added"); var results = []; for(var i = 0; i < elements.length; i++){results.push(elements[i].children[0].children[0].innerText)} window.location = "{InsertYourJiraURLHere}/issues/?jql=issueKey in (" + results.join(",") + ")";
Replace the {InsertYourJiraURLHere} with your Jira URL and run this script in the sprint report view console and it will show you the tickets you are looking for
Hi Adam, Pardon my ignorance but what is the "sprint report view console"?
Is anyone from Atlassian Team going to comment? Clearly the data is present so why can't we access it using JQL? Is this on the TODO list or the TOOHARD pile?
Vote for JSWSERVER-20097 to have this built into JIRA Server, or JSWCLOUD-16523 for JIRA Cloud, by default.
@Chris Rees I believe he means the browser console, which can be accessed by Inspecting the page.Board > Reports (left panel) > Sprint Report
Completed issues that were added after the sprint started will have an asterisk (*) after the issue key. Example:By pasting the javascript provided by Adam G, it will return the issues with the asterisk (*).
Apparently, they resolved this issue and the customer amazement that the data exists, but you cannot query it... they removed the asterisk from the Sprint Report.
Hey,
I dunno if that's what you meant, I pasted this link:
var elements = $("tr.ghx-added"); var results = []; for(var i = 0; i < elements.length; i++){results.push(elements[i].children[0].children[0].innerText)} window.location = "{https://kpaxlab.atlassian.net/issues/?jql=issueKey in (" + results.join(",") + ")";
in the JQL search bar under filters... but it's not working.
Any idea why?
Thanks!
it's a little work but could you not just add a label to those tickets and query the label?
Yes, but it requires users to manually add a label to every card (and to remember to do so) and also to manually change the JQL for each sprint because the label needs to be different for each sprint.
You can’t just have a generic “committed” label because if the issue runs over into a second (or subsequent) sprint there is no way of determining if it was committed in the first sprint or only when it rolled over into the second.
I too would like this query for my team. In the meantime, they added a Sprint Health Gadget that reveals the "Scope change" percentage. Clicking on this redirects to full page burndown chart with added issues.
lol
is there an @MOD here? I agree there Atlassian should specific if this is on the TODO or the TOOHARD list.. Clearly present, clearly a prevalent problem, clearly a blocker for fundamental use case of the app. What is going on?
I totally agree.
+1
I worked around this by adding a custom field called Sprint Commitment and creating an automation to set the field to Yes when a sprint is started, The automation also clears that field for anything that is open and not in the sprint that just started. The field doesn't need to be filled in by the user and I can run queries on it.
+2
Agree
@Jenn Sherman would you mind sharing how you set up your automation?
@Danielle Downs
This topic is now closed as the discussion has become outdated. If you have more questions or want to continue the conversation, feel free to start a new topic. For more details on why we close older threads, check out our Rules of engagement - Atlassian Community .
Thank you for your understanding!
It looks like you're new here. Sign in or register to get started.
