I wanted to know if you know how to handle screens where there are multiple boards in one project . That is to say, to avoid having the same fields of a request for a board to another board .
Boards do not belong to projects, and projects do not belong to boards.
Boards look at a set of issues that are selected by the filter. Those filters often are simply a single project, butthey don't have to be.
However, it's not clear what you mean by "multiple screens"? As screens have nothing to do with boards, but are defined as part of projects, I'm afraid the question is unclear.
No you do not. Again, boards do not belong to projects.
I assume you mean you have three boards that take their issues from part or all of a project. The fields you have in the boards are determined by the board configuration, and as you have three boards, there's three configs you need to look at.
The fields you are asked for when you create an issue are determined by the project you are creating it in. You need to look at the project's "issue type screen scheme" if you need to change those.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs