Adding a status after completed

[Nischal Sharma]

Here is the scenario I am experiencing:  At the end of the sprint, the development of a feature is completed but the product team is pending on the documentation or onboarding articles and hence we can't release the feature yet which means we can't change the status of the ticket to completed. This stops me from completing the sprint and the development team's work is not being accounted for. 

Is there a way that I can add a status after completed? I want to be able to complete a sprint but still be able to track its final release because the final step of onboarding articles/documentation is pending.

Or is there a better way to do this? 

[Jack Brickey]

How do you "release the feature"? Is the product team using Jira to track not development tasks, e.g. the documentation and articles? If so is this on a separate board or w/in the same scrum board? If the same scrum board are these in the same sprint or a later sprint? 

Without really understanding your process and environment I can't say what is best but will offer the following:

• Have the product team create their own Kanban board where they will capture a story to "release the feature". In the story they will have multiple sub-tasks:
  • Develop Feature
  • Test Feature
  • Create Documentation
  • Create Articles
  • etc.
• Arrange the swimlanes by stories
• Have your Scrum board for developing the feature. Link the development task that represents the feature linked to the Product Teams "Develop Feature" task.
• Optional: Use automation (addon) to automatically mark the "Develop Feature" as done once the feature development task is marked done.

Long story short Development can certainly work independently and 'release a feature' internally to the product team and have the product team accountable for release the feature to the customer. This is pretty standard means of operation.

Option 2: have a Done and a Closed status for your feature development task. Once features are implemented then move to Done (right-most column in Scrum board). Once all documentation, etc. is done move the issue to closed. You will, I think want to have a Kanban board in this case to show Done issue one column to the left of the right-hand most column and Closed as the R-H most column.

[Tarun Sapra]

Hello @Nischal Sharma 

You have a pretty common scenario and it can be dealt with quite easily with Jira.

You can have an status called "Dev Done" in workflow and this can be the right-most status in the board configuration so that when issue moves to this status then story points get burned so that devs know that their work is accounted for.

But the statuses after Dev done like UAT ready, Sales ready, In Prod etc can be part of the kanban release board which can be used by release team to progress the issue from dev done till release.

Hence you have two boards, Scrum board for dev teams and once the issue is done on scrum board then you have kanban board for release team.

A single workflow can be split across 2 boards very easily using JQL filter queries which fetch the issues for the board.

[Nischal Sharma]

Hey Tarun I really like your solution, can you tell me how exactly can I execute the following part of the solution:

But the statuses after Dev done like UAT ready, Sales ready, In Prod etc can be part of the kanban release board which can be used by release team to progress the issue from dev done till release.

Hence you have two boards, Scrum board for dev teams and once the issue is done on scrum board then you have kanban board for release team.

A single workflow can be split across 2 boards very easily using JQL filter queries which fetch the issues for the board.

[Tarun Sapra]

Hello @Nischal Sharma 

The workflow for the story has be such that it can be split across 2 board.

Open -> In progress - > In QA -> Dev Done - this is your Scrum board

Dev Done-> IN UAT -> In PROD -> SAles ready - this is your kanban board

Boards run on filters, which you can configure while board creation or later

https://confluence.atlassian.com/jirasoftwareserver0713/what-is-a-board-965542263.html

Th workflow statues which I have shared above are just for explanation you can choose the statuses which suits your teams the best.

[Nischal Sharma]

Hey @Tarun Sapra 

I am sorry I am not very familiar with board creation. I realize you are telling me create another board and then once the issue is on the right most of the scrum board they move to the Kanban board. Can you tell me how exactly I can do this step?

"Boards run on filters, which you can configure while board creation or later"

[Tarun Sapra]

Hello @Nischal Sharma 

Please go through the last link which I have shared. As you will need to create board and add a filter as explained in the link.