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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • 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

How to move a story to a defect when a custom field in the defect is required but isn't in the Story Edited

We have an issue when moving a Story to a Defect where we have a field called Injected Version in the Defects that is required. If the original Story has no sub-tasks we get the standard screen for the move, and any additional custom fields are displayed so that we can put in the required values. The Injected Version is updated and the move completes successfully.

However, if the Story has subtasks we get the bulk move screen instead of the simple move dialog. Again fields that were missing in the Story are displayed, but they also have the checkbox against them to retain the old value. Unfortunately, the Injected Version, which is a required field has the retain value checkbox checked, but this is also greyed out so that we cannot uncheck it to fill in a value. This blocks us from making the move.

The questions we need answered are:

  • Is this the expected behaviour?
  • Can we force the standard move dialog to be displayed instead of the bulk move dialog?
  • Can we enable the retain value checkbox so that we can uncheck it?
  • Is there anything else we can change to enable us to move the issue?

I forgot to mention, this is on JIRA version 8.9.0

1 answer

0 votes
John Funk Community Leader Dec 02, 2020

Hi Peter - Is the Injected Version field only available to Defect issue types in the context? If so, maybe if you added it to Sub-tasks as well you might not have it greyed out. 

It does not make sense to have it in the sub-task, especially as the defect is being copied from a Story. The Story's sub-task should not have the field, but neither would the Defect sub-task.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,047 views 8 28
Join discussion

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