Our organisation uses Jira Enterprise and I was assigned a project, managed by the Corp.
Our team develops three different solutions, name them:
I created three different Boards each one for one solution.
In the query for each board, I set a query looking for a component with the solution's name, for example:
project = MyProject and component = "Solution A"
This way, whenever one of the developers opens a new issue and sets the component as his solution, the issue appears in the right board.
My problem is, whenever I open a new issue and the "Component" field is not present, then the issue won't appear in the right board, and you have to find the issue and set the component.
Is there a better way to do this?
Hi @David Kon
You can add the Component field to the create issue screen, and even make it a required field to make sure new issues will appear in the right board.
Modifying the screens where fields are visible needs to be done by the Jira Admin, so in case that's no you, you'll need to make a request.
@Laura Campbell _Elements_ In the create issue screen, I do have a Component field.
The issue is in the backlog screen, when you quick add an issue in the bottom of an upcoming sprint.
When I do that, the issue is created but it doesn't have a component it goes to the general backlog and I have to open it separately and add the component for it to appear in the board.
@Aron Gombas _Midori_ as adding a component to sort the issues to the different boards works 95% for me, I would like to know if there is a better way to sort the issues, like by Epic/Solution or anything else.
Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events