Storing value to easily reuse/update them in ticket description

[Alexis Zankowitch]

Hi all,

I was updating my tickets to add some a link to my swagger hub so the developer knows what are the technical specification.
Then I thought, it would be nice to store the domain of this URL somehow and reuse it on all the ticket, like that if the domain change, I just need to change it once... and not xxx times 😅

I didn't find a way to do it, would anyone have any suggestions? Is it even possible? 

Cheers,
Alexis

[Ste Wright]

Hi @Alexis Zankowitch 

There are a few options - this is how I would do it:

• Create a Custom Field of type "URL Field"
• Create a default value for the field - so it's set at creation for all newly created issues
• Use bulk change to modify the URL if it changes for existing issues

^ This would allow for the default value to be set during creation - and using bulk change, modify the field in groups of 1000 issues at a time.

Let us know if this sounds of interest and would like some specific instructions on how to achieve it :)

Ste

[Alexis Zankowitch]

Hi Stephen,

Thanks for your answer. It sounds like what I'm looking for.
I think having a bit more specific instructions would help. I'm using Jira next-gen and I didn't find a way to set up a type of a custom field 😅

[Alexis Zankowitch]

Okay but let's say I have this field:
When I need to update the domain of the URL, will I need to then manually update all those URLs to provide the last part?

I want to have something like:

{https://mydomain/api/v2/} + user/message

Where I would have an easy way to update the first part:
{https://mydomain/api/v2}

[Ste Wright]

Hi @Alexis Zankowitch 

For Next-Gen, you'd need to use a "Short Text" field instead.

To add this in Next-Gen, you'll need to be a Project Admin and then...

1. Go to Project Settings > Issues Types
2. Choose an Issue Type to add the field to - if more than one type of issue needs this field, it needs to be added individually to each
3. On the right-hand side, select the field "Short Text" in the Custom Field section
4. Give the field a name - and set the default value as your URL
5. Press Save Changes
6. Go into each Issue Type which requires this field. The field will now be available in the bottom-half of the right-hand side as a "previously-created field". Drag/drop it onto each Issue Type's field layout which needs it, pressing Save Changes each time.

----------------

The default setting will ensure it is one URL value at creation.

If the URL changes, you would need to update it on previously created issues - you could either:

• Bulk Change: Search for the existing issues where the URL needs to change (Filters > Advanced Issue Search), then bulk change their URL if it will be the same value for all (3-dots Button > Bulk Change XX Issues)
• Automation: It might be possible to have a manual trigger-based automation rule which you can modify to include the new URL then trigger to update all relevant issues (eg. all open issues). You could also use this during creation to populate the URL if you preferred.

----------------

If the Automation rule sounds of interest, let us know some more specifics about how the URL would change (an example would be ideal), and I'll aim to provide some instructions :)

Ste

[Alexis Zankowitch]

Hi Ste,

Thank you, I didn'T know that feature Bulk update 👍 it's quite handy.

However, my concern about using you described maintaining my links were real. I can't use something like that because all the URLs will be different. So the easiest will be to change them manually if needed I guess 😁

Thank you again for your insight 😊

[Ste Wright]

Hi @Alexis Zankowitch 

There are a few other options possibly, depending on how the custom part of the link is generated:

• Automation: If the user/message is from another Jira field on the same issue, it might be possible to created the URL using Smart Values
• CSV Import: If you're a Jira/Site Admin, you could export the issues to update, make the modifications in a CSV file and re-upload the file

One of these might be easier than manual :)

Ste

[Alexis Zankowitch]

Okay,

I'll try to remember to try that once I'll get bored of updating those issues manually 😁

Thank you again for your time Stephen 🙏