Help needed with managing issues across multiple Projects and Sprints
Asked by Tomi:

Hello Jira Community,

I need some help with an issue I'm facing in Jira. We have a setup involving three projects:

* a customer ticketing project
* Department A project
* Department B project

Here's how we currently manage our issues:

1. In the customer project, we add labels (A or B) to issues to make them appear on backlogs of Project A and Project B respectively.
2. The board filters for Project A and Project B are configured as follows:
   * **Project A Board Filter:**
     * project = A OR (project = CustomerProject AND labels = A)

Same way we have it configured for Project B

**THE PROBLEM**

Despite these configurations, I am still able to move customer tickets labeled B into the sprint backlog of Project A, and vice versa. This results in seeing multiple sprints from different projects when managing issues. If I make a random mistake of putting a customer ticket with label A on sprint of Project B then I can see also the sprint of Project B on the backlog of project A.

**What I've Tried**

1. Ensured that sprint names are unique across projects
2. Verified and adjusted board filters for each project as shown above

Can anyone provide guidance or suggest additional steps to ensure that customer tickets with label B only show and move in project B sprints and same for A.

Thank you!


Answers:
author: Trudy Claspill
body: Hello [@Tomi](/t5/user/viewprofilepage/user-id/4837211)

The design of Jira allows for issues to be added to any sprint, regardless of the board in which the sprint was originally created. You can't prevent that from happening.

You can, perhaps, create an Automation Rule to detect that it has happened and receive an alert about it. I haven't tried to work out all the details, but you might be able to look at the name of the sprint to which the issue was added (if you are careful with your sprint naming) and determine based on the Label on the issue and the name of the sprint that it has been put into a sprint improperly.

comments: author: Tomi
body: Hello [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011)   

Thanks for getting back to me here. I have other issue:  

Let's say I have this type of filter for Project A:  

* project = A OR (project = CustomerProject AND labels = A

then if I go to backlog of project A and I click on create sprint it automatically creates with the naming "CustomerProject Sprint". I checked the board settings and board name is "Project A" so It's a bit weird.   

Thanks!


author: Trudy Claspill
body: The sprint names that are generated automatically are a suggestion. You can modify them. I think they are generated based on the names of other sprints created in that board, but I haven't seen any documentation to verify that.

Perhaps I'm not understanding your issue.

You said in your post that you want to
> ensure that customer tickets with label B only show and move in project B sprints and same for A

As I said, issues can be added to any sprint, even a sprint from a board where the issue itself is not within the scope of the board filter. You can't prevent that from occurring. You can only deal with it after it has occurred.

Regardless of an issue with Label B getting added to a sprint from the board that looks for Label A, in that board the issues with Label B still should not be displayed.

Can you provide screen images that show an issue with Label B showing up in a sprint on the board or backlog for the Board that uses the filter that specifies only Label A? Show the board/backlog pointing out that issue that has the label value B, and show the issue details itself so that we can confirm the Labels field has only the value B in it.


Tags: cloud

jira-cloud