Curt Holley Community Champion

HI @Kaushal Patel Yes, for anything to appear in the grouping, it has to have the relevant field populated (in your case, component). You could set up automation to populate components on to Stories etc from their Epic, but that still requires the Epic having the data.

@Martin Bouchard to suggest this feature, simply click the "Give Feedback" button (upper right hand side of a plan)

Check this out: Jira Automation: Complete Video Guides on how to S... (atlassian.com) You want a JQL option something like: issuetype in (story) and "Epic Link" = "{{issue.Epic Name}}" and statusCategory != Done

Hi @Martin Bouchard I take it you don't have a custom field "Remaining (story points)" or anything? You would just like it if there was such a field, rather than just the "Progress (by Story points)" field where you need to hover to get the remaining Story points. Sadly, this is not a thing..... The only way to try and set…

What I did @Mit Tolia was placed the Dependency Report specific URL in the iframe. But I've just checked, you can still navigate back to other views and then back to the Dependency report view. So yes, if you use an iframe with any Plan URL, you can still navigate around all the views for the plan.

Hi @Mit Tolia Best way (I know of) is to use the iframe macro. Simply paste the (URL) link and set the width and height. And!! You can still interact with it from the Confluence page.

It is true: Is it a true statement to say that in order to view the issue status on a kanban on a confluence page, the user has to be a licensed Jira Software user? To be more precise, they need permissions to view the issues that form the content of the Jira macro, to be able to see that content on a confluence page.

Hi @Apryl Harris Do those stories etc have the team field populated, or just the Epics? As to show up under a team, each issue needs the team field populated with that team.

Hi @Surfaraz T Welcome to the community! If the issues added to your plan are associated with a release, then the release should just be there. If you have added the whole project (for example) that has the release, then as long as the release has some content (Stories etc) that appear on the plan, If you go into the…

Atlas is a much cooler name.

Great blog @Mike Rathwell and one I can totally relate to. Not always easy to avoid "techsplaining" often just out of enthusiasm and forgetting how deep down the Atlassian rabbit hole I am in comparison to the people I'm discussing something with. But I always try to maintain a empathetic approach and keep it relatable.…

Hi @Javier Garay You could achieve this with Automation. Something like the below should do it. Up to you as to any other conditions, which issue types and link types are required based on your systems set-up

Yes, multiple teams can work on a single epic. If you enable "Roll-up/other" in the view settings of the plan you even get an overview of all teams involved. see mini example below. Here we have Abel Tasman with a story assigned, but Kepler are assigned to the Epic. Abel Tasman is rolled up and visible on the team field…

Right, a Jira Work Management restriction workaround. Of course if you were doing this in a Jira Software project you could have the custom field on the cards....and to that end, being able to create and control custom fields (without the need for automation to create a matching label) is an even better way to discourage…

Hi @Becky Brignall I think the 1st thing you should do is talk with a Jira admin at the company, as not knowing which hosting platform makes it hard for the community to assist. Plus, a lot of it will depend on how the Jira admin/s have configured Advanced roadmaps. They should be able to answer all the above questions.

Hi @Adam Morris Welcome to the community! Configure fields, view settings and filters until you have what you desire (as the new view), then click the down arrow (next to "Save this view") and select "Save as new view" and give it an appropriate name.

Hi @Rickhi.Seecharan Certainly @Mark Segall has covered off the automation beautifully, but what I am interested in is the Why? If you have a custom field on the screen of the issues that require it.... Why do you need a copy of that as a label? as it would be visible, searchable etc. as is. The only reason i can think of…

Can anyone see the issues in the plan? Presumably you can? What about other plans, are they working and are there any differences in their configuration?

Have you watched this? How Atlassian Uses Advanced Roadmaps - YouTube Regarding: "Anyway, my point was that multiple teams can contribute to a high-level objective. Assume for a moment you have a board that represents that high-level objective, and that several teams that contribute work towards that objective. Advanced…

Yes @Margaret Fross "-" are not helpful in filter names, which is rather annoying/out dated search behavior. I find having a word in the filter name that isn't likely to be in any/many other filter names is a great way to get concise search results for filters. 

True! @Gertjan van der Werken In which case @Juliya Kaplun-Eschenbach the only way (I can think of) to achieve the AND style (i.e. only show me issues with both of these labels) would be to build the filter and create a plan from it....so a different plan (which might not be ideal)...but I don't think it can be done…

I don't know @Dongmei Li but I would look at what issue source/s are used in the plan and the configuration of their filters. As unless your scrum team use a board that filters on their "Team" and that board is the only issue source in use on the plan it is likely that issues without the "Team" field populated could/would…

Hi @Ann Sciandra Welcome to the community! Do these users have access to see the content of the plan in native Jira? As AR permissions do not override Jira permissions, so despite you giving them access to the Plan if they do not have access to the Jira Project/s within the plan, they will not be able to view the content.

I agree with @Andy Gladstone . It is not the activity feed that is the issue here, but rather what is being put into Confluence and the way permissions are....not being controlled.

You do have to do it manually, unless you automate it. Common automation to use is: Trigger = Issue created User condition of "Reporter is "team members names" Action = Edit issue Currently the “Team” field cannot be selected from the “Choose fields to select” dropdown, so you need to add a Smart value setup like this into…

Besides that being a bad idea, I can only imagine it would only pull the content pertaining to the team you associated the board with. From an AR capacity planning prospective, what it is kinda dictating is; one team associated with a board that will represent their capacity for planning purposes. How that board is…

@Amir Baruch you can achieve these things via JQL and using the "Jira" macro on a confluence page or a dashboard gadget. i.e. fixVersion = XXX and "Team[Team]" = 999 set the display options of the macro to "Total issue count" Or use the Jira roadmap gadget and get a count of issues per Release/s as well as a progress…

I believe Atlassian are: * Aligning with Scrum thinking of "Capacity is measured by what is in the timebox known as a Sprint" and by associating with a board you confirm the teams core work/set of timeboxes. * Doing a lot of work around the concept of "Team" in Jira, as AR has introduced...more confusion. Plus, the team…

Something like this @Leslie Rathbone . The action can be whatever you want (transition or field update).

Hi @Juliya Kaplun-Eschenbach You just go to filters and multi select the labels you want to filter on, that works as an "AND" clause. TBH I unsure how I would go about doing an "OR" clause in AR....🤔