nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Script filter hinders creating new sprints.

Matthias Nickel

Hello,

I have multiple projects which are connected through different common epics, which are all in one project.

I use the following SQL Filter to show in a project only the epics, which the team has open issues.

issueFunction in epicsOf("Project = DCE") AND status != Done OR project = DCE

With this Filter, I can't create new sprints. In the board configuration is written, that the filter is to complex to show the involved projects.

Someone has a solution to that?

Accepted answers

Nic Brough -Adaptavist-

I suspect this is because the first clause could be pulling in issues from all sorts of places (even if you don't have data that would do that, it could do it). Project DCE might have one or more issues with "Epic Link = <an Epic in another project>"

Normally, you wouldn't draw Epics into a sprint, so I wouldn't be trying to use that filter for a sprint board.

It's a useful filter, I can see that, but I think you need something slightly different for your board if you're going to create sprints in it.

All comments

Nic Brough -Adaptavist-

Normally, you wouldn't draw Epics into a sprint, so I wouldn't be trying to use that filter for a sprint board.

It's a useful filter, I can see that, but I think you need something slightly different for your board if you're going to create sprints in it.

Matthias Nickel

I'm using Epic Links to connect many different projects. Like Matrix-organization. People belong to one project team, which works on many different projects.

Epic are our projects. That's why a connection is ncessary. All Epics are in mangement project.

If I use the following JQL:

Project = MGMTP AND issuetype = Epic and status != Done OR project = DCE

I can create sprints, but the single teams see all projects, even the ones they don't have any issues. As we have like 50 projects in parallel, i would like to reduce the number of shown epics.

Nic Brough -Adaptavist-

Ok, that's not what Epics are designed for, so it's not a huge surprise it is not working well.

I would consider moving towards a more Agile approach - a Jira project representing a project, Epics being (potentially cross-project) groupings of tasks, and a board being the place a team works. Then it would be fine for all teams to see everything as you're all working for the big picture, and a board can select only the items that the team owning it needs to see.

Matthias Nickel

Not that easy.

My company is part of a bigger enterprise. This enterprise holds the JIRA licenses and I'have to pay them for each project I create a monthly fee. This might be quite a lot with our more then 50 open projects.

We have been working with epics as projects( or bigger tasks, which have more like 300 single issues) for quite some time and now want to add more teams to JIRA. It's okay.

Every member of company can see what the otheres are doing. They have read only access to the other projects and can comment on issues. So we have a good overview about everything

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

scriptrunner

cloud

jql