I would like guidance on the best way to do this for Jira cloud. The project that I need to make this change in is not live yet so I could delete the field and recreate it. But I have a bunch of portal forms and other schemes that reference this field. I assume if I delete the field, I'll have to set all that up again. I am hoping there's an easier way to do this. Please let me know. The project is set to go live on Monday so I'm hoping someone can give guidance today.
@Amy_Hall When you need quick assistance, please post your question in the Atlassian Community. So many leaders are there to help.
I felt so bad that I missed your question, especially when you said you needed help because your project was going live on Monday.
Best,
Fadoua
🚀 With 𝗡𝗲𝘄 𝗗𝗼𝗰𝘁𝗼𝗿 𝗣𝗿𝗼 𝗳𝗼𝗿 𝗝𝗶𝗿𝗮 𝗥𝗲𝗹𝗲𝗮𝘀𝗲 – A Game Changer for Field Merging!
Jira admins, this one’s for you! The latest version of Doctor Pro for Jira now allows seamless conversion of:
✅ Single Select → Multi-Select
✅ Single User Picker → Multi-User Picker
✅ Read-Only → Text Field
✅ …and much more!
But that’s not all—Doctor Pro doesn’t just merge fields. It takes care of 𝗰𝘂𝘀𝘁𝗼𝗺 𝗳𝗶𝗲𝗹𝗱 𝗰𝗼𝗻𝘁𝗲𝘅𝘁𝘀, 𝘀𝗰𝗿𝗲𝗲𝗻𝘀, 𝗳𝗶𝗹𝘁𝗲𝗿𝘀, and, of course, 𝗱𝗮𝘁𝗮 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻 to ensure a smooth transition without breaking anything.
If you’ve ever struggled with custom field conversions (like I have 😅), this update is a dream come true! No more workarounds or risky data changes—just a reliable solution to make your Jira instance cleaner and more efficient.