An important field for our Jira issues is a "client ID" -- as we have hundreds of clients that have development requests.
Since nobody knows 100s of IDs off the top of their head, the field is set up thusly (for example):
McDonald's ID 11012
Burger King (ID 11233)
Wendy's --- 10838
There's a couple problems. Field validation is simply not there. Client "descriptions" vary in our systems and can change. There is no standard for where the ID is, if any. The simple solution is to use a simple, input mask "ID" as the master identifier, as it done in many systems.
However, how can you ENFORCE a 5 digit client ID, if the name has to be added to the field as well, for usability?
Is it possible to set up a custom field where a user CHOOSES the Client Description, but that is linked to a (validated, strict input enforced) Client ID?
Hi all Lets make this Friday fun really fun and post one (or more) of your best jokes! The joke can be about an Atlassian product, or just a really fun joke you want to share! I’m not the best j...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot