###Background###
I'm using Atlassian's Confluence to make a page where to display our teams subtasks. Subtasks that do not have the status Done will prevent the Sprint from being closed by the Scrummaster.
In our case, users do not assign values (like sprintvalue, assignee or status) with the same care as they do for stories and epics.
###Goal###
To make sure I have a list of all the subtask that would prevent a sprint from closing, I'd like to generate a list in confluence
All incomplete Sub-tasks -> that are part of a userstory -> which is the currently active sprint.
Currently, I have it set up like this:
type = sub-task AND status != Done AND parent =
The parent field only supports search by issue key or by issue ID, not by another query. This means that my original idea does not work:
type = sub-task AND status != Done AND parent = (type = story and sprint = "Sprint 1")
###Note###
I am in no position to use plugins.
Using Atlassian Cloud
###Answer###
As Kevin pointed out, and I already feared, this can only be done by using a plugin like scriptrunner. So far, the options seem:
Try and talk to admins, see if they can get clearance on a plugin.
Painstakingly input all the id's of the userstories in the JQL query. This will take a few minutes to set-up every sprint, but it is as much work as clicking every story for sub-tasks.
Try to find a way to visualize this in Jira itself. Since everything is bolted shut for users, this might not be as straightforward as it seems.
Unfortunately you will need a plugin to do that. I believe scriptrunner can do this, but there are surely others.
You might try an exotic workaround such as injecting data into your subtasks on transitions or other events of the parent issue. This way you can filter on the data in the subtask itself. However, I would not recommend this, as it can get very messy and it will be easy to get out of sync. Also, chances are large that you will also need a plugin for achieving that.
Another way of visualising this might be through a board in Jira. There you can visually see which subtasks are not done yet, and you might even play with quick filters, swimlanes or card colours to highlight some things.
Related
I am a new user of confluence, I participate in an workflow in witch customer support receives bugs, I report them to a central team of developers. Now, the thing is I am trying to create a way for the customer support team to have more visibility on the issues that I report, as in to quickly find out the status of a certain issues. What I have in mind is a confluence page consisting of a table of the issues extracted from Jira but I am having trouble reaching the exact end product that I have in mind. For example is there a way for me to make a column to this table so I can add comments for some issues? or can I categorize the issues by which pack of developers are they assigned to. Mainly I want to know if there is an alternative way of going about my situation and I don't see it because of my lack of experience.
Thanks!
Rather than adding comments in Confluence I would suggest you instead add them to the Jira tickets and then display them on Confluence.
The Jira Issues macro allows you to chose the fields you display. You could, for example, add a 'Confluence comment' custom field to your Jira tickets and make sure this is shown in Confluence.
As for categorizing issues, this is best done by using filters. The approach would be as follows:
Decide what categories you want
Create a filter for each category
Use the Jira Issues macro multiple times, once for each of the filters
We are migrating from an in-house tool to Jira for managing our scrum board, and we have concerns that I have been unable to resolve by searching the Internet. But you folks are smart, right? ;-)
Our current scrum board shows the usual swim lanes across state columns (for todo, progress, review, done). Each swim lane represents a user story, and has a link to (and a snippet of) the user story description in Jira. It also has a number of 'tickets' (these would be subtasks in Jira lingo) that start in 'todo' and move across to eventually end up in 'done'.
So far, Jira can do all of this, too (although creating sub-tasks is rather a lot more work in Jira than in our in-house tool). However:
When we commit code, we include a ticket ID in the commit message, and thus each ticket displays a list of commits that were done to complete that particular ticket / partial story. I haven't been able to find out how to do this in Jira -- if it's possible at all. Instead, it seems one must open a sub-task to see if there are any commits on it?
Each commit also shows its review state, which gives us an excellent overview of how close to done a ticket really is. I haven't been able to find out how to do this in Jira -- if it's possible at all. Instead, it seems one must open the sub-task, and drill down further into Fisheye(?) in order to see the review state?
In total, our tool provides a one-screen overview of the state of each user story, ticket, commit, and review state; and it's very lightweight to pull in new stories (from Jira) and add tickets. We fear that Jira is not able to provide such a one-screen overview, forcing us to open Fisheye in order to know whether a given commit has passed review.
Is it really true that Jira must be this cumbersome?
For reference, here is what a single ticket (subtask) looks like in our system:
And if you look at the whole scrum board, it's actually quite easy to get a feel for the number of commits on individual user stories and tickets, and the ratio of pending/passed/failed code reviews:
I agree with your fears when you say
We fear that Jira is not able to provide such a one-screen overview
In my experience (7+ years with Jira/Agile) I've not seen a such condensed view of information about a sigle user story even on a swimlane with relative cards.
Also in the Atlassian marketplace there seems to be no good plugin to solve your issue, even partially.
To make such move from your in-house tool to Jira retaining all you have there, I fear you should develop a custom Plug-in using Jira SDK to integrate with the agile boards.
It may be enough to start by developing a custom field to show what you need from a "ticket" (ie sub-issue) and trying to insert it into one of the three "slots" available for cards (I mean Rapidboard card layout configuration screen).
If you wanna try, start from here.
Another option to create a new custom field would be the Adaptavist Scriptrunner plugin. It will ease the building of custom fields: your new field can be written also in Groovy rather than plain Java. I've used it to build an extended status custom field (just to give the user an immediate big picture of it) that informs him in plain english and with stylish css colors why an issue is blocked or anything else relevant, getting data from other fields or linked issues that are not immediately visible to the user. IMHO, it is very similar to your problem.
In Jira, there's the "Active Sprint" view. You can expand/collapse all User Stories and Bugs to see the Sub-Tasks (that need to be done in order to close the bug/user story).
I would like to have a (quick) filter there to see which Bugs or User Stories I can work on. The requirement is that ALL Sub-Tasks of the Bug / User Story are still open.
Is that possible at all? A solution with multiple filters using each other would be fine too.
UPDATE: In other words, the filter should remove all Bugs / User Stories, along with their Sub-Tasks, that have at least 1 Sub-Task, that is not "open"
Thanks!
I´m trying to create a gadget for the Jira Dashboard that´s quite hard to accomplish.
I need to show a list of epics with time budget and the sum of time spent as columns.
The problem I´m facing is that the time logged is not made in the epics, but in the tasks or issues inside the epic (as I think it should be) and the column on "sum of time spent" is always empty.
This means, as I see it, that I have to be able to sum up the issues inside every epic and somehow show it in the empty column of the epic I need to see.
I created a filter and I´m calling it with the "filter results" jira dashboard gadget.
I tried with the Script Runner plugin and read the API it has, but still no idea how can that be done.
Is there any idea?
Thanks in advance for any advice.
I have looked for something exactly like this recently, and am surprised that JIRA doesn't have a way to do this out of the box.
Checkout Epic Sum Up. https://marketplace.atlassian.com/plugins/aptis.plugins.epicSumUp/cloud/overview It will solve the Time Budget question, but I don't know about a Time Logged solution.
See:
https://confluence.aptis.info/display/ESU/Time+Field
"How to search a Time Field by using JQL"
You might also find some useful features in the Tempo Addon.
https://tempoplugin.jira.com/wiki/display/TEMPO/Tempo%20Timesheets%20Documentation
Since you're looking to display something on a dashboard look under the Users Guide: Tempo gadgets area.
this works with the Plugin Timesheet
https://marketplace.atlassian.com/apps/294/timesheet-reports-and-gadgets?hosting=cloud&tab=overview
1) Add the Gadget to a JIRA-Dashboard
2) Edit the Gadget appropiately
but care that you
Group by: Epic Name
and choose for
Additional Fields: Original Estimate and Remaining Estimate
Consider to set Show Details: to No
This will look something like this:
(Remaining Estimate are the numbers Right from the Original Estimate-column )
I'm trying to use JQL to measure cycle times (the Control Chart has other issues), so I need to get the date that an issue changed status. I see that one can use the CHANGED keyword to filter issues that have changed status on certain dates, but I see no way to actually list the date of the change as a column.
Any ideas? How would you guys address this lack of visibility into cycle time data?
There is no simple solution available in JIRA at the moment. See the issue https://jira.atlassian.com/browse/JRA-12825 for the whole discussion. The argumentation of Atlassian is the following:
There exists a product Service Desk that implements the SLA feature expressed here.
There are reports and additional plugins available that give similar information to this. See the JIRA Suite Utilities which give you a UI for each issue to see the transition summary.
JQL (JIRA Query Language) was intended to select all issues that match a query, not to select special information to these issues. You have to use the configuration of the table, if it is included there as a field of the issue (which it is not).
In addition to the suggestions from mliebelt there is another at https://answers.atlassian.com/questions/128370/how-to-capture-date-of-state-change-in-jira. It requires JIRA Misc Workflow Extenstions and uses the "Copy value from field to field" function to capture the transition date in a custom field.
There is a plugin in Atlassian Marketplace called Time in Status just for that purpose. The plugin prepares a report on how much time each issue spent on each status or assignee.
Time in status is useless if need to count of Jiras that changed status on that day. Time in status widgets is useless for this