Kelly Arrey Expert

Late to the party, but why replicate the component value in the fixVersion field? You can filter the tickets based on the component and fixVersion fields. I'd leave them separate. Just my $0.02.

Here are a couple more things you might want to think about: * you may need one rule per workflow transition to keep the two issues fully synced - if the workflows for the two issues are different, that may add a bit more complexity * if your workflows have conditions or validators on the transitions, that may block some…

Thanks @Bill Sheboy, wish me luck!

@Siree @Bill Sheboy Sorry I'm late to the party - which platforms are you on? I'm trying to do this on cloud. Thanks.

Hi @Dave are you able to elaborate on this and give us an update? We use our own custom "Agile Team" field, which predates both the Portfolio "Team" field and the Atlassian Cloud "Team" field in our instance. Now we're trying to figure out how to implement teams in the context of Advanced Roadmaps. If you are able to share…

Update: The reason I couldn't get this work is because of JRACLOUD-73640. Fortunately, there is a workaround: * define the following filter: `issueLinkType = "belongs to"` * I saved it under the name `has belongs to link` Then, the filter I was originally trying to write can be expressed as: type = Feature AND (filter !=…

You may want to investigate the Structure addon from ALM Works.

My understanding is that Advanced Roadmaps implements the hierarchy above Epics by using the "Parent Link" field. There are somewhat oblique references to this in the documentation, but it's not very explicit. For example: * https://support.atlassian.com/jira-software-cloud/docs/link-issue-to-a-parent-in-advanced-roadmaps/…

@Abel Linebergerdoes "Mark as Done" set the Epic Status? There's an Epic Status field, separate from the Status field. We've added post-functions to our workflows to set Epic Status based on Status.

I also want to give a quick shoutout to two more apps which bring a lot of value to our Jira system: * SolDevelo's Worklogs makes it easy to generate monthly Time Spent reports. We combine this information with Excel exports from ALM Works Structure (which I mentioned above) to generate rollups of the time logged on…

Take 2: Here's the link to the docs again.

Hi @[deleted] here's what a similar rule looks like on our recently migrated Jira Cloud: The big gotcha that caught us was around permissions for the automation userid - here is the documentation: "The rule actor is the user who executes a rule. This user must have the relevant permissions to trigger the rule, and complete…

We at BlueCat Networks are glad we found ALM Works Structure for Jira - you can read about our journey here. We wanted to keep everyone in sync without adding friction to our Jira setup. Structure helped us achieve exactly that. We started with Structure on-prem, and migrated to the Atlassian Cloud earlier this year. Our…

Hi @Carol Low please count me in. Thanks,

@Arnd Layer is absolutely right, the UI becomes unusable as soon as your rule gets longer than one screen.

We migrated in March 2021 with the help of our local Atlassian Platinum Partner, Blended Perspectives, and haven't looked back.

Small comment on Mike's post - Jira & Confluence Cloud take the upgrade headache completely out of the picture - you get new function and fixes from Atlassian several times a year.

In my experience, SharePoint behaves a lot like a shared file system - documents are discrete files and you can navigate through the directory structure and hopefully find what you need. Permissions are a ongoing challenge in my experience - whenever someone shares a file, someone (or several people) will always say "I…

Thanks @Meytal BM !

@Vanessa BeckerWe were on Server 7.13, and the Boards pull-down was in the top bar. On Cloud the boards have moved - look for them in the pull-down at the top of the left nav bar:

Yes, we recently migrated to Cloud, and all the boards migrated successfully, even though there were multiple boards per project.

What @Darlene J said - sub-filters and hiding completed issues trip up many users.

Good one! Thanks again.

Thanks Dave.

Doh! Thanks John. Interestingly, the documentation says the IS operator is not supported for issueLinkType. That'll teach me to believe the docs :-(

Hi @Em Ditchfield Count me in please. Thanks!

+1 for Structure. We created an issue link type we call "Contain <-> Belongs to". We use it to link Features to Goals to Epics, e.g., * A Feature contains Goals* A Goal belongs to a Feature, and contains Epics* An Epic belongs to a Goal * Epics "contain" Stories, Bugs, Spikes, etc. via the Epic Link You can then build a…

We use two apps for this: * Structure Cloud by ALM Works - this lets us see the roll-up of estimates and time spent in a deeper hierarchy than just Epics & Stories (we use Features and Goals above Epics) * Worklogs by SolDevelo - this lets us see time spent by user, by ticket, by day/week/month Both support exports to…

+1 Clair.

Thanks Nic, was hoping for something less clunky, but that will work!