I have Stories - I have created a story workflow with the following status's Inprogress>>CodeReview>>QA>>Done
I have created a subTask workflow with the following >>Inprogress>>TaskDone
Now the idea is when all tasks are TaskDone we can move the story to CodeReview and then to QA and not the tasks. Is this possible? Like it is in TFS?
I need to be able to set the status of the story and not have it linked to the tasks?
When i try to add the column it says it is automatically calculated and can't be edited, well how is this setup and defined. This is really a decision breaker for us weather we as a corporation use JIRA or TFS.
Ok, most of that sounds right, you absolutely can have stories independent of tasks. As you've said, create two workflows, and use the workflow scheme to associate them with the different issue types. Issue types are independent of each other, so once you've got that setup, you will have independent flows for the two types.
JIRA Software does have a minor addendum - when you close the last sub-task of a story, it can automatically move the story to "done" as well, but other than that, if you want issue types to interact with each other, you have to code for it!
However, I'm stuck on two things:
I have setup two workflows one for the subtasks and one for the stories. I have just started my first sprint and I am ablt to drag subtasks into inprgress and TaskDone as defined in my workflow.
But Stories cant be dragged. So I went to edit the story and the "status column is not there" so i used the "Where is my Field Option" searched or "status" and the message says "The 'Status' field is not present on the form you are viewing" So how do I update the status of the story to be in CodeReview for Instance?
I think there might be two separate parts to this question.
First, there's the board behaviour - I'd like to skip that though, as I want to get the other stuff right, and make sure I fully understand what you've got set up.
So, the workflows. You have two workflows, as per your question. I'm going to assume they are names something like Story-wf and Subtask-wf. Can you tell me what the *workflow scheme* for the project says now?
I'm expecting/hoping for something like
Is that correct? If it's different, could you show us?
Excellent. Last few questions
I cant change the status of the Stories. I would like to automate the story status to code review when all tasks are done. But after that the story status I would like to have it manually set when code review is passed - I want it change it to QA once deployed and again when the tester gives the ok I want to change the status to done.
I had to send the comment from another account as i can only comment twice a day so I have to wait 24 hours, really TFS is seeming much easier and a lot better support but will give it one last stab :)
1) I want to be able to Drag the story from In-progress to CodeReview, Then TO QA, Then to Done.
2) Yes both the Story and task work flow use the same in-progress
3) No conditions on my transitions
Ok, your setup should quite happily support that, so we need to look at what is blocking it.
Can you pick a story that you don't seem to be able to drag between two of the columns (For example, one that's in Code Review and needs to go to QA). Could you then do these quick tests:
I read through this thread and @Gareth Knight is very clear to me, but I'm not seeing @Nic Brough understanding it. I'll give it a shot since I have the same problem now and I used to do this in Greenhopper easily.
In most Agile teams, you use users stories for features and subtasks for implementation details. Great, the sprint board lets us move tasks to in progress and then done under the heading of a story.
Generally speaking, there is a review process before calling a story done. There is no review process for each task.
So we don't have an "in review" column for the tasks.
When an engineering finishes the last task, the system asks if you want to change the story to "done". I say no. I want to change it to a status called "In review" and assign it to someone.
1. How do I do this? I'm talking manually, I don't see how it is possible from the interfaces in front of me to open the story and change its status (I cannot drag it since I can only drag the subtasks). I also can't "edit" it and change the status field.
2. If I can do it, how can I visually show the story status as "needs review" on the scrum board - this could be a color change, an icon, or worst case, just some text **Needs Review** written on the row/heading for the story.
3. Is it possible to automate #1?
I understand it perfectly, Gareth's project was not using the workflow he thought it was. I don't see what you think I am not understanding here.
On your questions
1. You drag it. Or click the workflow actions on the issue view. If you can't drag it or there are no appropriate workflow actions showing, then your workflow is not set to allow it - either there is no transition for it, or conditions are blocking you. Check your workflow. (You don't "edit" it because status is not a field, it's an indicator of position in your process, and you need to transition the issues)
2. Include the step in your workflow, use the flag field, use a custom field and set colours on the board display or just put the field on the cards.
3. Yes, with the automation or scripting add-ons.
Yeah... so basically you're saying that in "Agile" mode, with the default sprint board (if you're using sub-tasks, which it is set up to do by default), there is no way to drag a story to change it, nor is there a way to change it from the issue card. You have to go to the issue view for the story. Or a developer has to click on a different board, find the story again, move it, and then get back to the sprint board. Am I getting that right?
@Jacob Singh Hopefully you have this figured out by now. If not, try the following. From the board, do the following. Select the "Story" (not the subtask) that you are looking to modify the status of. Once selected, you should see the selected Story's details appear on the right side of the screen. Select the "3-dots" in the top right corner, navigate to the bottom of the options and select "More Options..." From the drop down, you should see "Workflow" at the top with the configured workflow status'. Select one (In Progress, Ready For Review, etc.). Verify in the Story details that the status has been updated to whatever you selected. You can also navigate to the story itself and update the status directly from the story (select the workflow status at the top of the story).
@Kyle Semon That is helpful - thanks for that. This, however, just takes away one step where I don't have to go into Issue View to change the status.
I see @Jacob Singh's issue here where we cannot drag user stories that are subtasked out. The only way you can drag user stories is if they do not have any subtasks associated with it. This is a poor design but we gotta do with what we got.
My question is: When moving the last subtask of a user story, you are prompted with the question if you would like to also move the parent (user story) to the same status. Can we change the default status that a user story can go to when all the subtasks are completed?
in my workflow - after moving the subtasks to done, I would like to move the User Story to a demo status that is one step before in my flow: to-do > in prog > awaiting PO > Done.
Hmm... I'm not sure of a specific configuration you can modify to simply change the default. However, I can suggest two things you can try:
1) Modify your workflow, as you've suggested, to require the story to go into a "Ready for Demo" status. You'll need to create the status and then add/modify transitions as needed.
2) Define Jira Automation to auto-magically move your status into the "Ready for Demo" status once all sub-tasks are "ready for demo, done, closed, etc." I have used Jira Automation for things like auto-creating new stories when the Sprint ends (or clone), automatically change the Story's status when subtask status' change (i.e. If subtask moves to In-Progress, then Story moves to In-Progress).
Hope that at least gives you some ideas on how you can make Jira more efficient and easier to use.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events