Curt Holley Community Champion

Hi @Villarasan The {{initiator.displayname}} smart value is looking for the user in Jira. So if the initiator is a webhook, that smart value will not work as the initiator isn't a Jira user in this scenario. Is the {{issue.summary}} working? if so, then perhaps {{reporter.Displayname}} might work??

@Villarasan No need to use JSON at all in this case. Just choose the Description field from the "Choose fields to set" picklist, then click the options (the 3 dots) for it and select Copy from trigger issue.

have a read here: Change how Advanced Roadmaps displays your timeline data | Jira Software Cloud | Atlassian Support and here: Create a new plan in Advanced Roadmaps | Jira Software Cloud | Atlassian Support

Hi @Raabe Tatiane Barbosa (DHL Supply Chain) If sharing, is there any reason not to just use the one issue, but visualise it/them across both projects via a board with an appropriate filter query? Saves the complexity of duplication and automation, as well as ensuring a single source of truth.

Hi @Dilani Kahawala Your "grab a time" link doesn't appear to be working, but I'd happily chat with you about automation.

@George Lerma What you describe is Advanced Roadmaps (available on Jira Premium)

Just share the URL with them (which is different to the "Share as" URL). Then they are taken to the plan and their permissions apply. Otherwise, using the Confluence option does give people with edit access the ability to "open in Advanced roadmaps" and edit.

Hi @Kenan Carames That can't be done currently, but isn't a bad idea. I recommend you click the "give feedback" button in Advanced Roadmaps and suggest it. 👌

Hey @Esther Strom Good question and frankly one I'm uncertain of an answer to. As for the population of the "lead", I've just had a look around and my guess is, this auto adding of the creator as "Lead" is new, as I am marked as lead of about 6 plans...the latest ones I've created. Older ones I know I created, the Lead is…

I don't think putting all of that in the "To" section will work. What does the rest of your automation look like (what conditions?) What happens if you just put the relevant email addresses in? as, although smart values are supported in the "To" field, my hunch is, the net result of using any in there would have to simply…

 I would use a if else condition to handle your custom field, If Notification type = Internal do whatever Else Notification type = External do whatever but then, how/where are you getting your email addresses from?

Further to @Bill Sheboy suggestions, if you are happy to receive whatever info it is you are after via email (from an automation rule), I've just got this working to report on the mentioned issue types in the JQL for the sprint that triggered the rule to run, by using the {{sprint.id}} smart value in the JQL.

Good pick-up @Bill Sheboy 👍

I've not experienced that behavior. if you select "Initiator", then the person who did the action that triggered the automation rule will get an email, but if reporter is what is configured, then the reporter should get it regardless of whether they were the initiator or not

Hi @Kyle Chalmers Welcome to the community! You can display up to 3 extra fields on the backlog view. Go to Board settings/Card layout/Backlog and select your fields. You should also be able to add them to your Advanced Roadmap Plans. Go to fields/manage custom fields and search for them and add them. Then you will be abe…

Hi @Rod Russell Welcome to the community! Change your trigger to Issue transitioned (configure "from any"...or whatever is relevant for the workflow involved, to "Done".

So, in other words, the ability to create a templated set of views (filters) that can be redeployed to new plans with different issue sources. As long as all your projects are configured the same (or very close), that could be handy. But what is filtered in from the Issue Sources could well compromise the effectiveness of…

So if you are triggering off the Risk being created, then the epic will need to be associated during creation for any such epic detail to exist for use in a "issue created" automation rule. But if that is the case then {{issue.epic.Summary)) maybe {{issue.epic.epicName}} (not sure, I haven't try that). Plus with Epic name…

Totally agree with @Danielle Green answer. Will add in, that it is the "Parent link" field that will link the Epics to the initiatives, so it makes sense to ensure that field is available on your Epics, Think Epic link field, but for the layer/s above.

I think you are right (and it is annoying). I would suggest changing the name of the filter (crazy, but it works). Give it a short, but distinct title. A word highly unlikely to be in any (or many) other filter names.

You could try using endofday () might help cover any timezone confusion due to time of running the automation. I just did a test and get the same results as using startofday ()

What happens if you just type "INEX" or just "22.3"?? I find just searching on the most distinct part of the name gets better results in these filter search windows.

The team concept in the People section is just a kind of virtual team. It is pretty much a one trick pony and that trick is, you can @ mention the team and all the members will get the notification. Atlassian are about to roll out a whole new (integrated team concept) as they agree/realise that the two not connected team…

Hi @Ian Rees You need to create Teams either in the plan or as a shared team via the Shared teams section. Have a read of this: Manage Teams in your Advanced Roadmaps plan | Jira Software Cloud | Atlassian Support

Hi @Laura Engstrand Sounds like there is more than one "Severity" field in your Jira. Are you not wanting to copy the same field? So your json would be; { "update": { "customfield_10211": [{ "set": [{"value": "{{issue.customfield_10211}}"}] }] } } Also isn't the field/s available from the "Edit issue" action list of fields?

This is interesting (and part of the problem with the term "Team" in the Atlassian universe currently). @Jack Brickey has focused on the notion of a team in the People section of Jira or confluence. Which I suspect is what you are after @Andra Vilcea ?? as that is a way of notifying them from the automation rule. Where…

@Timothy Padgett See my comment in this thread. Also @Roi Fine is telling it how it is.

@Unnikrishnan Ramachandran So is it not that the stories do not have the release in the fix version field?

Disclaimer: I'm talking about Cloud AR...am uncertain regarding non Cloud versions.

Hi @Bea Tea How does the roadmap generate dates from story points? it doesn't. The timeline data is generated by the date fields you choose to use in your Plan.