Filtering Out Sprints using wildcards

[Deleted user]

Hello. I'm trying to set up an alternate board on my JIRA project but I don't want the sprints from the alternate board to show up on the main board.

For example:

Development Board - shows only sprints that contain stories that are currently in development. Currently set up.

Issue Board - shows only sprints that contain issue and bug troubleshooting and correcting

If I make a sprint in the Issue Board, it shows up in the Development Board as well. I can filter out the single sprint, but when that sprint is completed and another is created, I'd have to update the filter as well. 

project = DEVELOPMENT AND  sprint != "Prod Issues December Sprint" ORDER BY Rank ASC

The fuzzy search "~" isn't allowed on the sprint field, and when I try to put the wild card identifier "*" in the quotes, it just comes back saying it can't find the sprint "Prod Issues*".

Is there another way around this?

[Trudy Claspill · Accepted solution]

Hello @[deleted] 

Welcome to the community.

Filters are meant for retrieving issue, not specifying which sprints to display.

When you use 

sprint != ...

...you are telling the filter to exclude issues where the Sprint field has been set to that value. That is different than trying to simply not show the Sprint among the other sprints on a board.

Boards are designed to show all sprints to which any of the issues within the board have been assigned. Example

1. Board A has the filter "project=X"
2. Board B has the filter "project=X"
3. In Board A create sprint named "Board A Sprint 1".
   That sprint displays only in Board A.
4. In Board A, assign issue X-1 to "Board A Sprint 1".
   Now that sprint displays in both Board A and Board B.
   Board B includes issue X-1 in its filter, so Board B will show the sprint to which X-1 has been assigned. 

This is necessary functionality because an issue can be assigned to only one Active Sprint or one Planned Sprint at a time. If the boards did not show all the sprints to which their issues are assigned then you could run into a problem when you tried to assign an issue to another Active or Planned sprint.

Can you provide more information about your use case for having an "alternate" board that spans the same issues as in the main board, and wanting to be able to have separate sprints for that alternate board?

[Deleted user]

After I posted this, I kind of thought about it in the context you described. What we are doing instead is filtering out production issues, which are all assigned to one epic, so that the sprint for production issues will not show on the dev board but will show up on the production issues board.