Issue created in one Kanban board appears in another board for an unrelated project

[Natalie Auer]

The issue is not appearing in the original board.

This has happened several times recently.

[Bill Sheboy · Accepted solution]

Hi @Natalie Auer -- Welcome to the Atlassian community!

A frequent cause of that symptom is a change to the issue, or board filters, so the issue is found by the different board's filter.

Please check the issue for any edits. Next check the boards' filters to see if they have changed.

Best regards,

Bill

[John Funk · Accepted solution]

Hi Natalie - Welcome to the Atlassian Community!

Issues/Cards appear on board based on the filter attached to the board. Cards are not really created in Boards, they are just created against a project. Then the filters for the boards determine where the cards show up. 

So, take a look at the filters for the boards to see what is being used to determine which issues should show up. 

[Natalie Auer]

Thanks, John and @Bill Sheboy . It sounds like from what you say and from what I've read in other people's questions, the filters will catch issues in other boards in the same project. But what if the issue is being sent to a different project altogether? (I don't have a specific example but will try to document it next time it happens.)

[John Funk]

It will be easiest to see the examples.  :-)

[op-fasc]

Hello, this is the closest article to my question so i thought the questions would be in right place here.

@John Funk You wrote "they are just created against a project" but i recognized, that also a bunch of other fields from the filter are paid attention.

Board JQL Filter 1: project = DEV AND labels = "[T]DEV#PM" ORDER BY Rank ASC

Board JQL Filter 2: project = DEV AND Team = DEV-PM ORDER BY Rank ASC

A board based on Filter 1 creates a ticket with the label from the JQL, Filter 2 doesn't set "Team = DEV-PM" to the issue. I think this is because "Team" is a custom Field, but is there any documentation out there to learn more about this? Like "which fields are supported", "how many labels can be set" and so on. 

[John Funk]

Hi @op-fasc  - Do you have a rule created that populates the Team field when the issue is created? Can you share a screenshot of that?

[op-fasc]

@John Funk Hello, no i don't have rules, i just created the custom field.

I don't know if i explained it correctly.

I created a board based on a JQL ("project = DEV AND labels = "[T]DEV#PM" ORDER BY Rank ASC"). If i use the "create issue" link below the issue list in the Backlog, i just put in the summary without opening the dialog. If i open the issue, then i see that the label "[T]DEV#PM" was automatically added and the issue appears within this board. This seems to be default functionality as i haven't created any rules for this.

If i try the same with a board based on a JQL with a custom field "Team" ("project = DEV AND Team = DEV-PM ORDER BY Rank ASC"), then i get a message like "issue created but not shown" and if i open the issue the field "Team" is empty.

And my question about this is, if this behavior is documented in any place, to find out more about it.

[op-fasc]

Update: I tried it with another custom field (single choice) and it worked. In this case it seems not to work with the field "Team" as it is a multi selection field for jira groups.

[John Funk]

There may be a bug related to that - I would open a support ticket with Atlassian as a follow up.

https://support.atlassian.com/contact/#/