Curt Holley Community Champion

I would create an automation rule along the lines of: Trigger = Version released Condition = Advanced compare where a certain prefix is used for the relevant Releases (see below) Action = Create Version and ensure the newly created version has that same prefix Perhaps {{version.project.key}} ? Hopefully this helps?

Sad, but true @Jamey Austin 

@NAYANA If you want to 'roll down' you can do that via Workflow Post functions (you may need to consult an Admin to get this set up for you) or via automation (Automation for Jira, Scriptrunner etc)

Great post @Jamey Austin and hinged off Dom's awesome article. To answer your question: Where I work I can see this transformation occurring. Yes, it's a work in progress, Yes! there are pockets of resistance, but as someone who has yearned to switch/be part of "the switch" I can say...."It is happening". I'm lucky enough…

What @Jimi Wikman says......or if you want to create a Plan for just the release then create a filter or 2 to just filter in the issues associated with the relevant releases, then create the Cross project release in there. Thus creating a Plan especially designed for this piece of work. JQL (along the lines of): fixVersion…

Hi @Svenja Lorenzen Nice graphic! and I think that about covers it for Team managed projects, but you could go deeper for Company managed. For example, You mention Project roles and a permission scheme as concepts, but your graphic doesn't show how those roles represent different levels of access within the same permission…

Bonus tip, beyond the great advice provided by @Jacob Vu Set your dependencies to be Sequential for your Plan. That way Advanced Roadmaps knows that is how you want to manage dependencies and will offer warnings and will auto-schedule with that in mind.

I notice in your Exclusions there are some issue types being excluded, that could be part of the problem as well. Try removing them from the exclusion list and see what happens

Hi It is hard to tell without having access to your projects and backlogs, but I've seen something like this before and the answer was; due to the Exclude any completed issues after = XX days (in the Exclusion rules section of the plans configuration) the completed work wasn't considered part of the plan, thus the…

If you mean via JQL, then yes. "Team[Team]" = then start typing the name of the team, select it and Jira will convert it to its ID number for you. If you mean in Advanced Roadmaps, Yes again. There should be filter for teams or, you can group by team.

@Suvradip Paul has pretty much nailed it...IMO. I'll add to his with: * Psychological safety is paramount. Establish and maintain it like a precious irreplaceable ingredient it is

That is an interesting JQL. Why the (project in (10017)) part? as surely that has to be the CS project or the query would not return anything due to the AND statement. I'm also frustrated by you not being able to get away with: Project = CS AND status in ("in review", "in test") as it really should work. For the record;…

Put the Project = CS back into your lookup issues action. and What is in your schedule? does it have any JQL configuration? If not, then add your same JQL there. That way only those 4 issues are part of the rule from the get go. Of course all of this does require getting your JQL to work. But totally agree with @Jack…

The JQL looks right. By having those multi-word statuses in quotations should take care of the confusion it is complaining about.

Exactly @Darryl Lee This is great example of measuring the wrong thing. If i were Jack, I'd either * leave * automate the population of 8 hours a day

Hey @Tanguy Crusson A colleague told me when I announced to her that we can now link to Initiatives in the Deliver tab, she said "We always have been able to". So is it just that we can now view the hierarchy and Delivery progress can roll up all the way to the Initiatives now?

Hi @Ron Caylor Interesting notion, but no, that is not currently possible. Not sure if it is something Atlassian are likely to pursue, as AR is essentially about the viewing of and manipulation of Jira issues. What do you see as the advantage of creating and then staging potential Jira content, outside of Jira?

Make it so @Tanguy Crusson 

Re automation: The sky is the limit. But off the top of my head, you could add conditional rules that "auto" set the custom field or label. i.e. If Due date is less than 2 weeks away and status is in "insert relevant statuses here", then update custom field to Amber. If less than 3 days away and status is.... then update…

No, you can't colour code the fields. Nice thought though!! We have a custom field with the RAG statuses. but it is just the words So whether you use labels or a custom field, both can be configured in your plan for colour coding, but the colour only ever shows on the timeline. Sorry this isn't more helpful.

Hi @Richard Way My guess (based on what you have said) is there must be a story (or something) assigned to ADT team, but in MF sprint (and or vise versa). Does that make sense? What are the filter queries for those teams Sprint boards?

Hi @Chris Elliott Welcome to the Atlassian community If you are happy for it to be done manually (though this could be enhanced with Automation, if you wanted) then you could just use labels "On-track", "Off-track", "At-Risk" and set up the plans view to colour by labels. This would show the colour on the timeline.

Hi @Braxton Wilkinson Welcome to the Atlassian community. My (very simple) suggestion would be to separate them out into 2 rules/emails. But beyond that, this may prove helpful: Solved: Can conditional operators be used in emails create... (atlassian.com)

Definitely encountered this and "as an Admin" am still dealing with it. I have recently been advised about the non-billing Authentication policy idea. But as we use Azure AD sync processes and SSO to manage access and controls, setting up such a non-billing Authentication policy would mean those users would be non-managed…

@Haris Vugdalic [JSWCLOUD-19398] Portfolio Team field has limited access from JQL within JIRA - Create and track feature requests for Atlassian products.

It is a known constraint of the team field. So yes! you need to be in JQL mode to use it. Not sure where Atlassian are at with any changes to the Team field, as it is not a sortable field either (which would be rather useful). Sorry I can't be of more assistance. Curt 

Hi @Darrel Jackson No, I think you are onto it/have i covered. We have a different screen for sub-tasks that doesn't show the Team field (which was confusing for a while) but I can confirm, * Yes, sub-task needs to be in the same team as it's parent. * All Sub-tasks inherit the team from their parent * You don't need to…

Nice one @Darryl Lee @Nick Barone if you can't evoke a global Automation rule, talk with your system admin, they will be able to empower it for you.

Hi @Nick Barone Welcome to the Atlassian community! Wouldn't be as simple as this? (see below) and if you also want to update other fields you could add an "Edit issue" action and set that up to your liking. Feel free to share more detail of the rules you have tried or the desired effect and we can assist you further.…

For your PMO Plan @Richard Way you need to add another issue/s for any project you want to see the Epics/Stories etc of. Either by adding Boards, Filters (that meet the criteria required) or even whole projects (just need to be careful not to overload the plan if adding multiple whole projects). The other key to all of…