The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • Is there a workaround to Clone existing Program in Big Picture to avoid issues with required fields?

Is there a workaround to Clone existing Program in Big Picture to avoid issues with required fields?

Sonja Klasen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 18, 2020

Hey all,

I want to clone a program box in Big Picture by using the respective wizard of the application. Unfortunately, I am getting the error message and reply from the vendor:

The most plausible cause of your problem are fields that are set as required in the Field Configuration Scheme, which is associated with this Jira project. 

Does anyone have a hint / workaround for this issue? Only workaround I received from SoftwarePlant Support was:

So, to walk around this, you can change fields from required to optional in Field Configuration Scheme associated with the afore-mentioned Jira project

 

Would be great if anyone would have a hint for me.

Best

Sonja

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Mateusz Sołowianiuk
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
November 25, 2020

Hi Sonja,

Unfortunately, I am afraid that there is no workaround for this situation. As a matter of fact, cloning is creating a new program and copying the whole configuration from the other one. The first operation requires that all Jira fields are set to be optional in order for it to be successful. 

Nonetheless, I will be curious to see if anyone else has found a way to work around this requirement. 

I hope that this clarifies. 

Best regards,

Mateusz Sołowianiuk

SoftwarePlant Support

TAGS
AUG Leaders

Atlassian Community Events