nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Will changing a workflow for an existing data request form change the status of older requests

Peter Morrisey

I have an existing workflow for our data request form. I want to change the workflow to streamline the process. I am concerned about older tasks, will changing the workflow to a status that is not associated with a previous task affect anything? My main concern is that we utilize JIRA service Management to communicate with requestors.

Accepted answers

Mikael Sandberg

Yes, any changes will affect all work items that are associated with that workflow. So for example if you remove a status and replace it with another one, when you publish the workflow you will be asked which status replaces the status that was removed.

All comments

Mikael Sandberg

Peter Morrisey

We can bulk make the changes from one status to another? We won't have to go through each task individually?

Mikael Sandberg

Yes, the change will be handled Jira when you publish the workflow, so you do not have to do anything other then setting the new status.

Screenshot 2024-12-19 at 2.05.01 PM.png

This is what it looks like in the new workflow editor, it defaults to a status in the same category, but you can select a different status if you like. Once you click Update workflow Jira will do the bulk change for you on all issues that used to have the status Resolved in this case to Closed.

Peter Morrisey

Thank you, very helpful

Joseph Chung Yin

@Peter Morrisey -

To supplement what @Mikael Sandberg stated, I would also recommend that you also need to focus on the following three items -

1) You may want to select a time to disable the notifications going out from your JSM project to ensure that you don't have any customized notification setup based on the WF (i.e. Automation rules etc..) during the WF updates.

2) Ensure all setup (i.e. boards/filter queries for the projects affected by the WF changes) incorporate the WF changes since it is a status change.

3) Communicate to all of your teams of this change, so no one is caught off guard.

Hope this helps.

Best, Joseph

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management