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

Clinic Name field that needs to be a fixed list not a free text

Bhavbhuti Nathwani Oct 06, 2018

Hi all

I have inherited a JIRA Service Desk Project.  The form has a Clinic Name field.  The names we enter in there are free text with browser based intellisense.  This means each support agent is typing in the same names differently.

I want to standardize this list so that the support agent is forced to select from the fixed list of clinics.

Also important, is that this field is not for user who are raising the ticket, it is only for support agent's use not for customers raising a ticket from the portal.

Please advise and pardon me for such a basic question but I am new to managing this project.

Awaiting feedback

Kind regards

Bhav

 

1 answer

0 votes
Hernan Montes Oct 06, 2018

You need to do a couple of steps for this, first you need to create a new custom field of type single select list, you can call it the same as the old one but I do suggest giving it a unique name so next steps are not confusing.

After creating the list field and adding the desired options, add it to the current screen scheme the project is using, normally the create screen and the edit / view screen are the same, you will need to see if they are different so you can add the field to the needed screens.

After this is done, you need to search for all existing issues with the old field not empty, export the list to a spreadsheet and then decide which values are going to be mapped to the new values if they are not the same, once you get the mapping done, do a search for each value to be changed and do a bulk edit, here you will change each of the values once, from old field to new list field, you will do this bulk change for each value that needs to be changed.

Once all bulk changes are done, you can go ahead and remove the old field from the screens so users will no longer have it and use only the new list field.

Remember that you will need a re-index after this change.

Take an XML backup before this change just in case.

Let me know if you have any other question.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Jira Service Desk

4 changes to queues and issues you don’t want to miss

Hello Atlassian Community! I'm Tania, a Senior Product Marketing Manager for Jira Service Desk Cloud! I'm excited to announce some exciting improvements coming up for those who work with queues and...

594 views 9 13
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