Curt Holley Community Champion

Hi @Vivek Karna Welcome to the community 😊 As @Kristopher Perez has alluded to with his rule. Linking the issues is key. You may well have known that and are doing that. But as you never mentioned the conditions under which a Project A would move a Project B issue, I thought I''d point it out.

Yeah @Simmo The "primary incident" field that is only part of the Post Incident Review" issue type in JSM.

Thanks @Bill Sheboy Good call. Though I'm having issues accessing the API currently. But, it isn't a JQL searchable field. Can't find it in Custom fields , Issue linking.... So I'm doubting it 🫤

Hi @Irena_Matraku Welcome to the community Not really, not in AR. But if they are using the Jira time tracking fields or Story points you can write a simple JQL with all the team members and ORDER BY Assignee. Then ensure you have the columns for the relevant fields (Original Estimate, Time Spent, Story Points) and there…

Use {{issue.fixVersions}} or {{triggerIssue.fixVersions}} as per: Jira smart values - issues | Cloud automation Cloud | Atlassian Support not {{triggerIssue.fixVersion}} or {{issue.fixVersion}}

Hi @Ellen Yudt See this: Solved: How to add a custom field to Filters in Advanced R... (atlassian.com)

Hi @Ellen Yudt Welcome to the Community! Sadly, there is not. That said, assuming you are on cloud, adding the members doesn't really do anything currently. It may well in the future and having someone added will be a requirement to take advantage of this upcoming change:…

Greyed out means that those issues do not meet the current filter criteria but the plan is configured to "Show full hierarchy". Untick that, and the greyed out stuff will not show.

Hi @Christine Byrer I agree with @Wade H there is no right way, just the right way for you/your company. That said, I am fond of separating out any levels above Jira Epics and keeping the team/standard projects with just the standard Jira hierarchy of Epic, Stories/tasks whatever/Sub-tasks.

Hi @Nina Barley Can these people edit the issues in native Jira? Can they do the linking or change dates on the Jira issues themselves? If you have access, have you checked how the Advanced Roadmaps permissions are set and any influence that may be having on them?

One question!!! that makes it tough @Andy Gladstone . I'd want it to be a conversation starter, so probably something like "What would he have liked to do next/what was left on his bucket list?" (Assuming I'm talking with him is some post 2016 magical "Lunch" opportunity) 

Hi @Cash Coyne Not sure what your "Theme" field is (or is supposed to do), but I believe if you add the "Parent Link" field to the relevant Screen schemes, then that will be where the linkage is occurring. Parent Link covers all the hierarchal linking for levels above Epic.

I'll keep this real simple. * Discourage the use of emails as a way of raising a ticket in JSM * Make the portal as helpful as possible (Customer focused layout, KB Articles, Conditional forms) * Encourage incorporating Assets into all your ITSM practices * Automate, Automate, Automate

I've always found this to be related to the fact that it is using Updated in conjunction with Status category = Done to decide what is hidden and when. So, if someone adds a comment, changes a field value on a long closed and hidden issue, it will reappear on a Kanban board as long as it still meets the filter query…

"World leader" is an interesting concept. Who qualifies for that title? and in what field? With that in mind, I'll go leftfield and say David Bowie. As I see him as a world leader of Music, Art, Fashion, Reinvention and Innovation. From cross-dressing to Internet banking, Bowie = World leader. Not to mention, Oh! the…

@Collista Lewingdon No, the one in your screenshot will not work on epics and tasks, as it is the Sub-task based one. Use the "When all stories are completed → then close epic" template and tweak to work for your issue type(s) and "Done" workflow status(es).

Big Picture @Doron Katz BigPicture - Project Management & PPM | Atlassian Marketplace

I tend to agree, though certainly it is the Team managed element that makes it so flexible. But like any Team managed project, they can wreak havoc in the environment around field names, workflows and automation rules. It would be ideal to have both available. That said, if they (Atlassian) made some of the JPD fields…

Hi @Collista Lewingdon Epics are not the "Parent" of sub-tasks...Tasks and Stories etc are. If you want an Epic to close when all Stories (or tasks...whatever) are complete. Go to the Automation library and use "When all stories are completed → then close epic" as the template to get you started. If you wanna do the…

You can have a Sub-task for every standard issue type, if you set it up like that. Blocked by is a link type and so is not hierarchal. But the beauty of linking issues IS that is hierarchy agnostic. If you want it built to your spec, go ahead: Rename Epic to be Story Create a new issue type called Epic and put it at level…

Hi @Doron Katz Welcome to the community. This is certainly not built-in to Advanced roadmaps. Currently only team level capacity can be visualised (as is the Agile way), I don't something like future headcount (assumptions) would ever become put of the product natively.

Hi @Amanda Chapman If you add Use Case above Epic, then it will be the parent link field that you use to hieratically link up from the Epic to the user case. The parent link field is what is used for all levels above the Epic (level1) So to answer your question Does the Parent link always have to be an Epic? No, in your…

Hi @Joseph Chung Yin Linked issues certainly are supported in AR and have some great visualisations. See below, the "lines" view of them, where you can even click on the line to see details or remove the linkage. The thing is, they do need to be configured and that is done in Settings/Dependency settings. The configuration…

@Benjamin Peikes I think most people perceive Stories to be "the work item/where the work gets done". Also, Features are the higher level piece of work and they require multiple stories to complete them. See the SAFe model. Scaled Agile Framework (SAFe) - Guilde to Scaling - Agilest® Features are at the program level,…

This is great. May I suggest the ability to copy If/else branches and refactor, instead of having to recreate the same format with one element different each time would be another awesome enhancement 👌

Hi @Amanda Chapman I would leave your "Use case" issue type as a standard issue type and as you have suggested link to the relevant Stories. Possibly even with a custom link type that would make for easier filtering options and could be added into the Dependencies section of Advanced roadmaps for filtering and other…

It makes sense from the prospective above level 1 has never existed before Advanced Roadmaps (in Cloud), so it is uncharted waters. Free to create new and exciting levels. Where the Epic to standard issue type functionality is some of the oldest chartered waters in Jira, and as such adding new levels in-between would…

Yes @Benjamin Peikes the functionality that has always been associated with the Jira Epic, will always be at level 1. The only difference is now you have the option to call it something other than Epic. I doubt Atlassian have any intention of offering the ability to build out further hierarchal levels that reside…

Change it to "Add Components from Trigger issue"

Hi @Rob Horan The only way I can think of to achieve this would be to create a custom field. A date picker, not date and time picker (see: Enable custom fields used in Advanced Roadmaps in Jira | Jira Software Cloud | Atlassian Support ) The get an automation rule to populate it at creation. Yes, there is a compromise,…