Is there any way to create a global variable/field that can be used across all projects?
Hi @David Loszewski ,
Would a custom field work? https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/
Most likely not since a custom field is issue specific. I want a global variable that I can set, and then compare against from any project using automation for jira.
Ie.
Global variable = 4.5
Then in automation for jira, if issues custom field = the global variable value, edit issue fields, etc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @David Loszewski ,
Custom field can be configured for global (for all issues). Custom field can be considered for your requirement.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Even if you configure a custom field as global, it will be available for all issues, but its value will be specific to an issue.
This is what David tries to avoid.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
but won't it be a different value for each issue? I want it to be the same value for all issues
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can set default value for this field. So automatically , whenever the new ticket is created the custom field value will be set to the given default value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sreenivasaraju P I think the default field idea will work. You should post as answer so I can accept and you can get the credit! thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Using the default field is a slightly clunky workaround, but it's what I'll be doing :) Thanks for the idea, Carlos!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just realized that there is a "Create variable" action!
(You could add this as the first command in your chain of commands, and it would effectively create a global variable that can be configured in the rule.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.