To finish activating your workflow, associate the workflow scheme it's in with a project. If an issue type is not defined in the project's issue type scheme, that specific workflow is not used.
Click Switch Scheme and select the relevant workflow scheme from the Scheme list.
Click Associate to begin the migration process. Each issue needs to have a valid status, so you may need to assign statuses to a select number of issues after you switch workflow schemes.
A Jira project must always be associated with a workflow scheme, since all issues must move through a workflow. To disassociate a custom workflow scheme from a project, simply associate that project to the default workflow scheme instead.
This is what I found on the instructions but it doesn't match with my layout.
the point 4 (workflow) it doesn't appear.
I ran into the same problem, and wasted a lot of time banging my head on the wall. But, finally, I figured it out!
See this documentation:
https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-workflows/
It states the following:
Before you begin. This page contains information for how to set up and configure company-managed Jira projects. Company-managed Jira projects have different features and capabilities than team-managed Jira projects.
Fortunately, I was just setting up the project I wanted to change the workflow on. I deleted it, create a new one as a "Company Managed" project rather than "Team Managed", and then this "WorkFlow" item actually appeared in the project settings!
Hi @Robbie,
Are you using a next-gen project?
They do not support workflow configuration yet https://community.atlassian.com/t5/Agility-articles/Everything-you-want-to-know-about-next-gen-projects/ba-p/894773
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I agree with Bastian. This post also tackles workflow configurations in next-gen projects: https://community.atlassian.com/t5/Jira-Software-questions/Configure-workflow-Nextgen-project/qaq-p/950599
Carlos
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bastian & Carlos,
Yep! it was like you said.
I used the new way without read the instructions! :)
I'm going to use the old project with customize workflow.
Many thanks
Roberto
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Robbie - please don't forget to click on one or both of the "Accept Answer" buttons for Bastian and Carlos' answers so others see the flag in their search results. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Larry, because I'm super new to this community, can you tell me where is the Accept Answer button? I guess it's already flagged.
Sorry about that. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Roberto, normally there is a green box with the text 'Accept answer' above the answer(s), but I don't see it for this question...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Carlos,
I guess Is like you say.
I can't see either.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Was just noticing this myself. I'm going to post about this question in a channel frequented by Atlassian Community staff to see if they can take a look at it. Glad to know I'm not the only one that doesn't see the "Accept Answer" buttons.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@LarryBrock my guess is this was originally posted as a discussion and moved to be a question. When that happens, the Accept Answer buttons disappear. That's a known bug. 😕
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
Good Morning.
Can anyone please let me know if we can associate a workflow to an issue type only (ex: Bug/Defect).
Below is my scenario:
Wanted to have a separate bug workflow which applies only to issue type bug/defects. Because a bug will have re-testing, re-open, closed, rejected and removed status and those will not be applicable for the project status.
So created a new workflow and assigned that to a bug/defect but that isn't listing in active workflows are not assigned to a project for a issue type bug/defect only.
Can anyone please let me know if you have an idea please!
Kind Regards,
Keerthi.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.