Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Unable to publish an inactive workflow

Hi All,

Am new being a JIRA admin and I have just created a workflow for defect lifecycle.

This workflow appears in "Inactive" section and when I search around I don't have an option to publish it to make it active and start using in a project.

I have also created a Workflow Scheme and a similar issue exists in that too, unable to publish.

Can someone please assist with this?

Thanks,

Eranga.

2 comments

Hello @Eranga Perera ,

 

Welcome to Atlassian Community.

  1. Please go to project Settings.
  2. Go to Workflows
  3. Click on "Add Workflow"
  4. Choose "Existing"
  5. Select The newly created Workflow. Click on "Next"
  6. Associate with "Defect" issue Type.
  7. Click on "Finish"

 

After that you may need to Re-index issues , If some Defects are linked with old Workflow.

 

Thanks,

Anvesh

Like John Funk likes this

Hi Anvesh,

Thanks so much for your prompt response.

We do have a workflow that we've created and using a BAU style implementation.

What am trying to achieve here is to introduce a new defect workflow which can be used for little projects that we are going to manage and also looking to integrate with Zephyr.

At the moment what am facing is am unable to assign the new defect workflow that I have created to type "Defect" so that I can use this workflow for upcoming projects and do not want to override the existing workflow they are using for BAU operations.

Am not sure I've explained this well. And am happy to send you screen shots to further explain.

Thanks again,

Eranga.

Hi , 

Sorry , i'm not getting you.

You do not need to make a workflow active directly or "publish" it, the active/inactive display is not a flag, it is simply an indicator of whether the workflow is in use or not.

To use the workflow without affecting existing projects, create a new workflow scheme (or, probably easier and quicker, copy an existing one that is mostly correct), and map the new workflow to "defect" (keep or add other mappings as required).  You can then associate the new scheme with any project that needs the new workflow for defects.

Hi Nic,

Thanks for getting back to me on this. 

I have now created as you have advised above however when am trying to associate the new scheme with the project its asking me to set new field values replacing the old and the statuses I want are not the same I require.

Please see the attached screen print here. My fear is if I go ahead change this current status to match to new workflow would it make changes to all other items which uses that workflow.

image.png

 

Please advise

Thank you very much

Eranga

The change of status must be done because you are removing the existing status from the workflow and hence the issues need to be changed to use the new workflow.  It would make no sense to have issues in the status "closed" while their workflow is "open -> in progress -> done" - the closed status isn't in there.

When you publish this change, the status will only need to change for the issues that are changing from using the old workflow to the new.  Issues across projects will only be affected if you're changing their workflows too.

Thanks so much for your response and I have got that sorted out now.

Much appreciated @Nic Brough _Adaptavist_ @Kagithala Babu Anvesh 

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Bitbucket Smart Commits vs. Genius Commits - What's the difference?

If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...

120 views 0 2
Read article

Community Events

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

Events near you