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

Moving issues from One project to another. Target has required fields that Source has not

Hi there

We are in the process of migrating a NexGen project to Jira classic. In the classic (target) project there are a bunch of required fields. Those fields are not necessarily filled out in source project. When doing the migration via bulk move, Jira asks for the fields to be filled out. We are talking about hundreds of issues. So I changed the Field configuration in the target to deactivate all the required fields. Migration goes smoothly. But after reimplementing the original Custom field configuration on target, I was expecting Jira to ask users to provide missing fields at the next transition. Unfortunately it's not the case. What should be the approach ?

 

Thanks

1 answer

1 accepted

0 votes
Answer accepted
Hana Kučerová Community Leader Jan 13, 2021

Hi @Kamel Meftah ,

your users won't probably be able to edit and save these issues without adding all the mandatory fields filled, but they won't be forced to do it during transition.

If you want to forced them to add the values during transition, you can temporary add screen with all the necessary fields to the transition.

The second option I can see it to do some sort of bulk updates of your issues.

Hi @Hana Kučerová ,

Thanks for your reply. The transition solution is not an option. That will imply putting the validator in each possible transition of the different workflows.

Bulk update is ok when you have limited options for the values and very few custom fields impacted. But that's not the case.

Hana Kučerová Community Leader Jan 13, 2021

What about to ask your users to help you with this - distribute the work between more users - create some filters for the issues, which are missing values, and ask your users to update all the issues, which are assigned to them...

Like Kamel Meftah likes this

Without any other magic trick, that's what is going to happen. But that was last resort. Thanks Hana

Hana Kučerová Community Leader Jan 13, 2021

Another possibility - you should be able to update your issues using csv import, see here. But I don't know if preparation and test of such file won't take more time then do it manually.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
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,071 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