Boards and Teams (Artists vs Coders) Tasks/Issues

Oliver Jones

Hello,

I'm new Jira and I'm trying to setup a workflow for my project and teams.

I can't seem to figure out what the benefits of creating new boards does, they all seem to hold the exact same tasks/issues?!

Ideally, I would like to create a Board for my Artists, and a Board for my Coders; and I have done just this.

However, when I create 'issues' within the Artists board, they also show in my Coders board, and vice verse. I would like to keep issues for the Artists only visible in the Artists Board, and likewise for the Coders.

So it seems that creating a new Board just simply mirrors everything, which seems a bit pointless and very messy to me?

---

I come from a Trello background, so to me; when creating a Board, and adding Tasks; those tasks stay and are children of this Board. However this isn't the case for Jira. It seems as if the Issues/Tasks are children of the Project (rather than board-specific), and are shared across all Boards, which makes no sense to me?

Could someone please explain the best way to do this is?

Petter Gonçalves

Hello Oliver,

Can you please let us know if you are using next-gen or classic project boards?

Also, can you please provide us if both Artists and Coders issues are on the same projects? If that's the case, you would need a field to differentiate an Artist issue from a Coder issue. You could use different issue types, for example - Tasks for Artists and Stories for Coders. 

Better explaining:

In Classic projects, you can edit the JQL filter of the board in order to display different issues. So, let's suppose that your coders are using Stories to track their work and you would like to create a board to only display their stories. Here are the configuration steps:

- Create the board > Navigate to the board and click on the three dots icon (...) at the top-right corner > Board settings

- Click edit filter query > add the following parameter to the board:

project = xyz and issuetype = story

If you are using a Next-Gen project, I must tell you that this template was configured to give a simpler solution for small and less complex projects. The Next-gen boards are based on the project issues by default and it does not give you the functionality to change the issues returned.

That been said, you are correct to say that creating new next-gen boards will always mirror the same issues of a project, not making any sense to create more than a single board per project.

Let me know if the information above helps you.