We have a check box custom field on a project that we need to split out into two check box fields. How best to do this that will retain the values on the current issues and be split into two fields going forward? My intuition is to rename the current field and disable certain values and create a new field with the disabled values from the current field. Make sense?
Thanks for any help,
Here's our configuration:
And where we want to end up
*Checkbox Field 1*
*Checkbox Field 2*
I went with my intuition as stated in my original post. Created a new checkbox field for the disabled values from the original checkbox. Renamed the original field in line with the client's request.
The business use case went something like this. The client has a field on her project for Department(s) that are associated with a Project issue type. Some of the department(s) the client was responsible for contacting and some of them it was the responsibility of the reporter/requester to contact. She wanted to split the original Department(s) field to break the list out into two lists aligned with whose responsibility it was to contact them.
Does that make sense? I mocked up my solution in TEST and had the client review it, they were satisfied so I duplicated it in PROD.
I am not sure I understand the question - can you confirm that you have something like this on the issue:
Our checkbox field:
Option 1 (ticked)
Option 2 (ticked)
And what you want to end up with is
Our first checkbox field:
Option 1 (ticked)
Our second checkbox field:
Option 1 which was 2 on the old field (ticked)
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs