nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Split the ability to create different type of issue, on the same board.

unknown

Hi everyone! Here is the guestion:

Is it possible to split the team on the same board?

1 team "Devs"

2 team "QA team"

The next question: is it possible to confiqure the type of issue that can create these teams?

Here the example:

QA team capable to create ONLY "bug" issue type, and Devs team can create Bug AND Task AND Sub-task issue types. Can I split this ability for two different teams?

Thanks all of you for work here ^_^

Accepted answers

Marc -Devoteam-

Hi @[deleted]

Yes you can, use the Team field or create a custom field single select to differentiate the teams.

I urge to use the teams option.

Second, no there is no option to split the usage of issue types in a project.

Any user on the project is able to create an issue based on the types available in the project.

Divya Shree_6o7ujf

1) You can create labels inside the issues and separate both the teams. Create Dev and QA labels. Go to your board and now add quick filters:
i) labels = QA ii) labels = DEV

Now using these two quick filters you can split both the teams.

2) You can try using automation for this. Create two groups in the user management. Using these two groups and respective issue types, give the conditions in the automation rule.

All comments

Marc -Devoteam-

Hi @[deleted]

Yes you can, use the Team field or create a custom field single select to differentiate the teams.

I urge to use the teams option.

Second, no there is no option to split the usage of issue types in a project.

Any user on the project is able to create an issue based on the types available in the project.

thank you! ^_^

I do agree, but have a BUT.

Labels are case sensitive, and can typos will create new labels and issues then could still fall outside the scope.

example:

Qa, qa, Dev would all be considered different labels and JQL on qa will only provide results based on qa and not include QA and/or Qa.

unknown

I've heard about this. It's gerat to read all of your solutions. This help me to keep in mind all posible ways. I am new here so it is not so easy for me to keep all info at ones. Thanks!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud