Currently, we have our projects set up with multiple boards. My goal is to have one board that only shows issues with the tag "mothership" in the label. As well, I would like to pre-populate that label field with "mothership" if I'm creating an issue while in the backlog of that board. Currently we have a project that's set up to do this but I cannot replicate it for the new board of the new project.
What I've narrowed down to is this:
Can someone please give some guidance on where this behaviour could be coming from and why it only works for the PE project?
Hello @Kelvin Lui
Welcome to the Atlassian community.
Clicking the Create Issue button at the bottom of the backlog will default to having you type in just the Summary of the issue when no other fields are required to create issues in that project. The dialog for issue creation will open only if there are other required fields for that issue type in that project.
Does the PE project have other required fields for creating a new issue?
I have tried a similar situation on a Scrum board for a Company Managed Software project. When I use a comparable filter (project and labels=X) and the issue has no additional fields required during creation, I see that after typing in the Summary the issue is created with the label.
In what manner have you confirmed the issue is created without the label? Does the issue remain displayed in the Backlog or does it immediately disappear?
Is the Labels field displayed in the issue screen after the issue is created?
You're right! Thank you so much! I went through so many steps that I mistakenly associated the pop-up issue creation screen with the label issue. I can confirm that although the issue creation screen doesn't pop up in the new board (which is fine), it does indeed tag the mothership label.
Are there any articles that explains why the query auto-populates the label field? Just wondering if I can use this for other things.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not aware of any documentation on this topic, but I have not scoured the content looking specifically for that topic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.