Is there a FREE way in JIRA to require that a parent issue can't be
advanced to a state until the children (sub-tasks) are advanced to an
equal or greater state?
FOR EXAMPLE: Suppose an issue has 4 sub-tasks: 3 in PROD state and 1 sub-task is in UAT state. I shouldn't be able to advance the main issue to PROD until that 1 sub-task is advanced to PROD first so all my sub-tasks are in PROD state. Same thing with CLOSING an issue when sub-tasks are OPEN.
There is no such specific post function out of the box from Jira but you can surely write your own plugin or Groovy script(this needs script runner plugin) which can do this job.
Simple condition like, you cannot close parent issue unless sub tasks are closed can be achieved as simple as this: https://confluence.atlassian.com/jirakb/preventing-issues-from-being-closed-while-their-sub-task-are-still-open-724928276.html
Other helpful discussions can be referred here:
https://answers.atlassian.com/questions/142131/parent-issue-needs-to-close-once-sub-task-are-closed
https://answers.atlassian.com/questions/262497/close-subtask-when-parent-is-closed
https://jamieechlin.atlassian.net/wiki/display/GRV/Post+Functions#PostFunctions-Autocloseallsubtasks
Thank you,
Yes, under the transition Conditions. Add a condition Called "Sub-Task Blocking Condition.
Then, select the statuses the sub-task requires before the parent tasks can move forward. You can select more than one, so select the statuses that are equal to or greater state. Heads up though: the selection page shows all existing statuses, not just the statuses used for that workflow.
Do this for each step you want restricted.
Related
I've had three items assigned to me for the current sprint, two of them categorized as "blockers." The third item, in 'done status,' had a requirement change today.
I checked on what "blockers" mean, and they are things preventing you from getting a task done, right? So how can a goal itself be a blocker?
Also, I've been forced to do a lot of context-switching this week in the past. This is due to support for a couple of projects. However, it keeps me from settling into the blocker tasks.
By the way, I did get one blocker task reclassified as "major" due to effectively going over the Scrum Master's head. However, it was a non-customer-facing pilot project that I had been pulled into a call on. So both of the blockers came about this way.
The third project had a scope change due to a bug discovered (not my code), which affected me.
I'm not clear how to handle all this. Any ideas?
The word 'blocker' does sometimes get used as a way to describe a very high priority task.
e.g. This ticket is a blocker for another team, so we must get it urgently fixed.
I agree this can be confusing!
When a task (Task_1) is a 'blocker', it means that without solving it, another task (Task_2) in the team cannot be completed.. so 'blocker' tasks usually have a high priority.
So you can imagine both tasks have to be done in series, like in an Airflow DAG:
Task_1 >> Task_2
Our developers work from Sprint Boards, and they drag tasks into Closed stage. However, this leaves stories as New / Active when all tasks are done, and there is no easy way to know if story has all tasks completed
Is there a way to auto-close story when all tasks are done (without any additional plugins)?
Is there a way to identify what stories have all tasks closed/resolved?
Work items have independent states. Most of our experiences will not include automatic updates based on hierarchy. Either based on parent to update child or based on child to update parent.
You could refer Taylor's comment in this thread--User Story status closed but child Task still active?
Even though there is not any build-in solution, you could use some 3-rd party tool to auto change parent states: TFS Aggregator .
Another sample using Webhook to handle this. Detail solution here: https://twitter.com/danhellem/status/1173614918333030400?s=20
which leads to: https://github.com/microsoft/azure-boards-automate-state-transitions
I have a portfolio set up for my Project in Jira. It contains 6 or 8 epics and there are varying numbers of Jira tasks associated to each epic.
The Portoflio Scope view shows the epics and the tasks under each epic but the progress bar displayed for each epic or it's linked tasks does not show progress, even for epics where 90% of the tasks are marked resolved or closed.
All tasks have Original Estimates, Remaining time and those that are resolved, fixed have time logged against them.
I cannot find anything useful int the Jira Docs for tracking progress. I presume this is down to some smal config option or some feature of the epics or tasks but I cannot for the life of me work out what it might be.
We are using the cloud version of Jira.
Any ideas?
OK, so we found the reason behind my issue. By default the portfolio Scope view was showing epics for my project with the 2 releases I was interested in. There is a More option on this filter and under that was Completion date.
By default this completion date seems to be since the beginning of: Current Sprint. This meant that all tasks marked resolved or closed were excluded from the list of tasks under the epic on the portfolio board...hence, no progress.
I'm not sure why tasks listed as completed under the current, active sprint were not listed based on the default Completed filter though? Maybe it is because the portfolio was set up based on a Project rather than a Sprint Board?
Anyway, changing the completion date to something else then meant the completed tasks were included under the epics and I am now seeing lots of green progress bars!
Perhaps it is more psychological than programming question:
We use JIRA with Greenhopper in our work, so when I receive new tasks I see them at the Agile Board for current sprint. For every sprint I have a LOT of tasks, after I have fixed, for example five of them I set their state as need test and these tasks go to tester (he has not only my tasks to test as usual). If these tasks are tested and all is ok they closed by tester. The problem is - that I could not see how many tasks I have done. When they are closed they disappear from my Agile board and I see only new tasks there... Imagine - yesterday you have completed five tasks for current sprint, but today chief adds ten more tasks in this current sprint for you.
So: Number_Of_Tasks - 5 + 10 = Number_Of_Tasks + 5.
And thus the Agile Board has no visual progress for me - it grows in size. This is very demotivating
In short: How could I view my done tasks?
You probably have the "Hide Done Issues" button ticked.
Go to Agile > Task (Greenhopper Agile plugin needed)
Above your Task board. One is "Hide Done Issues". Click/Unclick that.
Your Done issues will now be displayed.
Imagine - yesterday you have completed five tasks for current sprint, but today chief adds ten more tasks in this current sprint for you.
As for this, your chief needs coaching. If you are doing SCRUM, then the "chief" (whoever that is) should not add extra work to your sprint. If you finish your tasks early, you should pick some off a teamate who might have run into trouble, or you can test his stuff. The point is to achieve the goals you (the team) have set for yourselves. If everybody is done, then the sprint finishes early. Good for you!
You can finish and replan the next sprint or teamates should pick off stuff from the backlog themselves.
The danger of a "chief" assigning you stuff is that these micro-managers may not have a detailed understanding of what has been done, what is to be done and what is un-tested and might be reopened by a tester.
You can use a Jira query as a filter. The query itself would look like this:
status WAS "Need Test" BY currentUser() AND status = Closed
... yes, quite like SQL. ) Here's the official documentation link.
Is it possible in TFS that workitem can have two state options when created. For e.g
I have a requirement in which when bug is created it can either be DEV state or CCB state.
But I am not able to figure out the way how to do this. All I was able to do is to put one redundant initial state as "New" to start with. And from New state I can either go to DEV or I choose CCB.
Any inputs will be really appreciated.
Thanks,
Mayur
Mayur - it's not possible. You can choose a different Reason at the time of creation (eg: Build Failure, Regression, etc), but a work item only has one initial state.