Curt Holley Community Champion

Nice one. I can relate.

OK, cool. Final question; Why the two projects? wouldn't it be easier to run all Opportunities out of one project? Perhaps spread over multiple Boards/Teams/Components. Anyway, have you tried what Bill suggested over here? Automation for Jira - Automation to link tickets w... (atlassian.com)

You could also do this via a Post Function in the relevant Workflow. Example: The field Fix versions will take the value from Fix versions. Source issue is the parent, destination the sub-task. See here for details/inspiration: Configure advanced issue workflows | Atlassian Support

Hi, may I just check I have your scenario right? Are you saying you always need a ticket (with the same opportunity ID) in both Projects A and B? or You need to have matching tickets in A and B only when an opportunity ID is present? or....something else? Another question. Is one project considered the master (where the…

Hi Ebi Have you brought this to the attention of the Jira admins of your Jira Instance? As they should know what has happened and why.....then either correct it or explain the "why" to you. I presume this is effecting everyone? I also wonder if it is only impacting the project you are currently in, or many/all projects.…

Right. I missed the epic linked to another epic part. Complicated situation, well handled 👍

HI I'm only familiar with the Cloud version of Automation, but ignoring my trigger/insert whatever trigger is relevant....wouldn't something like this work? plus no scriptrunner functions required.

Yeah, 1 and 2 are annoying. I know Atlassian are working on making the Team field more flexible, but I'm not certain it will resolve these or not. 3 can be done now on cloud at least (via a macro). Looks like it is available on Server/DC as well? Sharing and exporting plan data | Advanced Roadmaps for Jira Data Center and…

Interesting scenario. Not sure it can be done as simply as you are thinking (happy and interested in being proven wrong though). Your "Add to development" screen is kinda as complex as doing a manual cloning process, so.... Best I can think of is: Replace it with "manual trigger" based automation. This would really simple…

Yeah, you should have something like See here for more details: View development information for an issue | Jira Software Cloud | Atlassian Support

I presume the Jira issue key is mentioned in the code? Can you see the evidence of the branching in the Jira issue in the development section?

A good day = Writing automation (via Automation for Jira) to make people Jira experience more pleasurable and accurate. Working on other value add initiatives like getting the Deployments API working with Azure DevOps Yaml based release pipelines. As well as educating people in the joys of visualising their content in an…

The general lay of the land in my part of the (Jira) world, is; Each ART (we work in the SAFe model) has a Project, and Team focused boards are set-up using Shared teams as the extra filter criteria. There are exceptions, but this is the norm and what I recommend. Yes we have examples of worked shared within a project and…

@Hans Keller you have had way too much fun "anonymizing", but as a Dr Who fan, I love it. Brilliant!! In terms of a practical example of Team association, it is simply replace filtering the board board via Component/s with filtering via the Shared team. See example: project = LSTT AND "Team[Team]" = 213 ORDER BY Rank ASC…

Great question @Dave I was wondering the same thing.

Hi @Hans Keller You sure can....presuming you are on Jira Cloud??? If so, you can do this via Automation for Jira. Trigger = Issue Created Condition = User condition (where you then add the team members) Action = Edit issue (at this stage the Team field isn't available in the dropdown of fields to select, so you need to…

If you don't have scriptrunner, then I think you will have to name each link type that you are wanting in scope. Something like: project= ABC AND "Epic Link" = Epic1 and status != Closed or (issueIsDependentOn = Epic1 OR issueIsDuplicatedBy = Epic1)

@Alex Bernardin True!!! @Dave Releases suggestion might be worth thinking about. But that may depend on how Releases are being uses across your Projects/teams currently. have a read of this as a starter on Releases and versions | Jira Software Cloud | Atlassian Documentation

Not sure this will help (seeing as you use a plug-in to provide the WSJF fields....if they are not supported, then.....) But we created our own fields and use Automation for Jira to do the math. These fields are supported and can be added to a Roadmap Plan. it works a treat! Like a spreadsheet with formulas. But we are on…

From what I can see/tell, it is because the timeline settings have an end date prior to your current sprint. Regardless, play around with the the date range and see if that fixes it.

Hi @Kat Warner I would be happy to share some use cases we have around Risks, dependencies and WSJF sessions that use Automation for Jira and Advanced Roadmaps on Jira Cloud premium. 

I believe it is legacy functionality from the old (Portfolio) UI. It does nothing.....currently. I'd like to think in the future what you are after will be possible with Advanced Roadmaps. Fingers Crossed!!

Right! that makes sense @Giorgi Tsitsvidze glad to see you have it sorted as well. Nice one!

So, when issue created you want an email to go to someone advising they should transition that issue? If that transition is known, then automate that. or modify the workflow so that issues (or that issue type) defaults to the right status. If certain issues need to be transitioned upon creation, then the current workflow…

To do this you will have to either flatten the hierarchy (as you have described) and have Milestone and Epic share level two. This would mean any linking of any issue types at the same level (Milestone, Epic in this case) would need to be linked via a link type and not a hierarchical style link like Parent or Epic link.…

From what i can tell, you are wanting the transition to occur based on clicking a link/button in an email. But what would the trigger be to send that email? If there is a trigger to send an email to transition an issue, then the better option would be to get the automation to do the transition (as alluded to by @Alexander…

HI @Brittany Sudlow We don't appear to have Anchor/Smart links/New move options or hyperlinking yet. Should we? We are in new Zealand (end of the earth) on cloud, so......???

Well @John Funk that works a treat. Love it!! and sure enough, wrapped up in "all your fancy stuff" summary does indeed get produced. I had raised it with atlassian and their advice was to duplicate the JQL in a branch, which didn't solve the problem, and meant an email was generated per issue. I've added in the key and it…

Thanks for that @frother good idea. I tried it going into the comments section of an issue via a manual trigger. No go. Yet, when I try {{Key}} or {{URL}} and even better {{Key}} and {{URL}}.....no problem. Just {{Summary}} doesn't seem to want to work with {{lookupIssues}} Best I raise it with Atlassian I think.

Yes! I thought about including that very definition, but wanted to stick to the one word rule :-)