Default start date to sprint start

[Richard Way]

I have the plan settings set to use the sprint start date if no start date is set. And I added the Sprint to the list view to verify it was pulling correctly. The sprint shows "EXT" and that it's not in the plan. 

The challenge though is that the Plan covers multiple teams, each team has their own board, some of those boards cover multiple projects. 

Is there a way to set the scope to multiple boards and then set a locked filter to limit the plan to just the appropriate Initiatives? 

[Danut M _StonikByte_]

Hi @Richard Way,

Not sure if this is possible to do in Plans. But WHY do you need this?

If you need it for tracking progress across multiple teams (or across  epics/initiatives/themes/features involving multiple teams), you could solve the problem by using an app from Atlassian Marketplace that is capable to generate cross-team stats.

If you consider using an app, our Great Gadgets app many useful diagrams/charts/stats for this.

For example, it offers a Release Burndown Burnup Chart gadget (with Forecast) that uses a filter/JQL (not a board) as input. 

So if you configure it with a filter/JQL that returns the issues in your initiatives (so issues from multiple boards):

issue in portfolioChildIssuesOf("POR-101") or issue in portfolioChildIssuesOf("POR-102")

... you will get a cross-team overall burndown chart.

Similarly, you can get many other statistics at the global level.

See these articles to make a better idea: 

• https://community.atlassian.com/forums/App-Central-articles/How-to-display-the-progress-of-Epics-or-Initiatives-in-Jira-or/ba-p/2858840
• https://community.atlassian.com/forums/App-Central-articles/How-to-track-scaled-agile-SAFe-projects-in-Jira-with-Great/ba-p/1929694

Hope this helps.

Danut. 
 

[Joni Johnson]

@Richard Way Not sure if this will assist in what you are trying to do with Plans. When I see EXT in Plans, it means I need to add the Teams to the Plan. As far as a locked filter, you can create views to pull specific data which I'm not sure if this is what you are wanting.

I have setup plans using filters to pull in specific work because I don't want to exceed the 5,000 limit of plans. We use ScriptRunner which allows you to pull children and parents which help quite a bit. From an Atlassian webinar, they recommend using the projects and boards yet with the number of teams and initiatives we have in a given year, we exceed the 5,000 limit so use filters quite a bit.

[Richard Way]

We have Premium, so we can use this for a filter:

issue in portfolioChildIssuesOf("POR-101")

Makes it super easy because all of our major initiatives are documented in the Portfolio project. So each team working on them adds their epics from their projects to that Initiative. 

But since we're talking multiple teams, it would be multiple boards. And while POR-101 might have a couple of epics and a dozen stories across them all, those boards could have hundreds of stories at any point in time. I haven't hit the 5k limit, but it becomes a mess well before that point. I don't need a PM from one project to have to sift through every other project and support ticket just to find their info :( 

[Joni Johnson]

I'll be interested to see how others reply on the locked views. Good luck.