Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Use a Field Smart Value For Destination Project when Creating New Issue with Automation

We have a tier 1 support project which we use as initial triage for client and other reported issues. Once the ticket has been vetted, it is transitioned into an 'escalated to...' status, which triggers a SR script to generate a new linked issue in the appropriate development project, as identified by a select list custom field.

We recently purchased Automation Pro, and I'd really love to replace the script with an automation rule, which is easier to manage. To that end:

1) Is it possible to use a smart value to set the project in which a 'create issue' action generates an issue?

 

2) Is it possible to do any type of string manipulation on a smart value? Right now this custom field contains a string with the name and project key of the destination project - I can alter this if necessary, but I'd love to not need to. I can get into the context if needed, but I cannot use a project picker field here.

4 answers

2 accepted

0 votes
Answer accepted
andreas Community Leader Jun 15, 2018

Hi Haddon,

Great to see you found our docs on text functions!

Unfortunately though I don't think you'll be able to implement number 1 currently. We don't support smart-values yet in the project and issue type fields. We've got an issue to track this already at https://codebarrel.atlassian.net/browse/AUT-948 

We've got quite a few higher priority items in our backlog at the moment so it will be a while before we can get to this, but we'll let you know when we get a chance to work on this.

Cheers,
Andreas

0 votes
Answer accepted

Posting this for posterity - while you cannot use a smart value to solve this problem, you can use the JSON\additional fields option to do this. In my case, I had to do some string manipulation to get the key out:

{code}
{
"fields": {
"project": {
"key": "{{issue.L3 Escalation Project.value.substringAfter(\"(\").remove(\")\")}}"
}
}
}
{code}

I think I fished my wish for question 2 (its amazing what you find if you look) so I guess the actual question then would be "if I can use a smart value to set a project, will it take the key or the name?"

Use smart value like this:

{{issue.ProjectPickerCustomFiled.ID}}

Where ProjectPickerCustomFiled is the name of your custom field that is an issue picker.

.Id .Key .Name  are all field that you can take from a project picker

Suggest an answer

Log in or Sign up to answer
TAGS

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