Is it possible to assign Stories and Subtasks (within the same project) to different workflows? We don't test subtasks, only the actual stories, so we'd like to have an Pending->InProgress->Closed workflow for subtasks but a Pending->InProgress->InTesting->Closed workflow for stories. Is this possible?
Nic's pretty much nailed it on the head, ultimately you'd want to configure a workflow scheme to manage the issue type-to-workflow associations. More info here: https://confluence.atlassian.com/display/JIRA/Configuring+Workflow+Schemes
Not quite what I expected. I have created two separate workflows, one for sub-tasks and one for the rest. I create a series of subtasks under a story, the end result is both workflows are merged into one where you can only move the sub-tasks to the columns that were part of its dedicated workflow.
I am looking to have two separate workflows, one for the devs to move the tasks through the development phase (preferably grouped by story or an easy way to see what story the tasks belong to) and one to move the stories through (e.g. testing, PO review, UAT etc).
Can this be done?
K, I may not be following and consuming too quickly but...
if you have two WFs and you want one to apply to the Story and the other to apply to the sub-task then you simply need to assign the issue type to the appropriate WF.
Story = WF1
Sub-task = WF2
i must be missing something?
Hi, I have set up the following workflows:
Created some stories and sub-tasks and move a few along their workflows then when I view the agile board both workflows have been merged into one:
TIO BAU Workflow is ToDo->In Development->Testing->UAT->Done
TIO BAU Sub-tasks workflow is YoDo->InDevelopment->Parked->Done
I am looking to have two boards, one for each workflow and if possible the sub-task workflow to group the sub-tasks by parent story.
now you are confusing me but ignoring the previous and focusing on this new detail...
why would you want two boards, one for stories and one for sub-tasks? If you map the statuses associated w/ the various workflows to the proper columns then dragging and dropping will adhere. The workflows are not merged into one it is just that both issuetype exist on the same board because you have not excluded any issue types in the filter.
If you are dead set on having one board for Stories and one for sub-tasks you can do that (see below) but I don't think you will like the results. Stories and their sub-tasks belong together.
p.s. have you looked at using Swimlanes by Stories? Maybe that would work for your goals.
In any event this topic is drifting from the original thread and I fear will confuse future users. To that end, if there are further questions, it might be best to open a new thread.
Separate boards aside, I encounter a problem when using the single board so as to have a single source of truth/view of work flow across a team when using "stories" & their WBS in the form of "subtask".
I have coherently mapped the possible states of "Story" & "Sub-task" into desired columns when configuring the Board. However as soon as I instantiate a Story with a Subtask, the board re-flows that story out of its current context & priority order for execution/flow and sets it apart into its own swim lane for that story. This is wrong on multiple levels for any execution team
- for one breaks the order of stories/tasks/bugs that they will likely have agreed at planning and thus the visual representation on the board
- The swim lane sets the "Story" in the "ToDo" column when right next to it it echos back the "In Development" state.
- What is the value of mapping the states for the jira types story, task, sub-task if they aren't respected by correctly landing the item in the corresponding column when using them as a combination (story & sub-task)?
Have I missed something with the board configuration to have this effect?
- I have included the view of my board configuration, incase some one can better reason than I have been able to for the resulting view.
Here is my Board configuration for the column/states
The Jira Software Cloud Team has been busy working on a simple, secure, and reliable way to integrate your build and deployment information from Jenkins with Jira Software Cloud. This means you don’t...
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