So I'm creating automation based on
Trigger = Version Created
Then it creates a issue with a Summary of: {{version.name}} Release Artifacts
Updates the start and Due date fields with:
{{version.startDate}}
{{version.releaseDate}}
So far so good.
But how do I get the automation to update the Fix Version field so that the newly created issue is assigned to the newly created Version?
I've tried some json options but can't get anything to work (not that I am very good with json.
Any ideas?
Answer is as per my last comment to John above. When i initially tried this, I just hadn't hit enter before moving on/saving and thus the entry never stayed (or saved)
Hey Curt,
Can you share a screenshot of your rule?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @John Funk sure.
this is what I've got working, If I add Fix Version as a field to populate the options are all related to procuring the version an issue. Where in this case (as the version has just been created), there is no other issue to reference. So I tried some attempts at json, but I couldn't get anything to work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any Ideas @John Funk ? It's like it needs a combo of json and smart value, but i can't get anything to populate it.
Seems odd that the "Version Created" trigger can't then create an issue that is associated with the version that triggered the event.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Don't worry @John Funk the answer was simple. Just had to hit enter after placing {{version.name}} in the fix versions field.
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.