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; } } }

Hide certain components in Jira

Jurica Petricevic

In a good part of our projects, the allocation of Issues happens through components, but also the allocation of subtasks. The components used to assign a Issue to someone in the Subtask should be hidden when creating a Issue.

only some selected components need to be hidden. hidden components have the same name across all projects and projects use the same workflow.

We have automation, JMWE of tools for something like that. Can someone help me?

Best regards

Jurica

Accepted answers

All comments

mogavenasan

Hi @Jurica Petricevic,

I'm assuming that you are using the Component's Default Assignee. Unfortunately, it's not possible to exclude Subtask from the Component's Default Assignee.

However, since you have automation, maybe you can consider implementing the default assignee based on Component via automation(not sure which Jira apps you are using) or JMWE(Workflow post-function - Set field value).

I hope that this helps.

Thanks,
Moga

Jurica Petricevic

there are 3 components in each project that serve as a type of Issue assignment but also a viewer of done subtasks. It was one big problem and it should stay that way but it should also be hidden when creating the main ticket. I use these components in Automation rules and no one else should see them. but I cannot hide them in Jira.

Thanks for your help.

Thorsten Letschert _Decadis AG_

Hi @Jurica Petricevic ,

components are related to the project and not the issue type(s), so you're not going to be able to 'hide' certain components for certain issue types.

If you want to restrict a field to your sub-tasks, you should consider switching to a dedicated custom field and restrict its usage/availability to your sub-tasks. While the assignment might get a bit more complex (no more assign to component lead' but 'if option A then assigned B, if option C then assignee C, etc.) I don't see another option here.

Cheers
Thorsten

mogavenasan

Hi @Jurica Petricevic,

I'm quite confused here, if you want to hide the Component field, then no users can fill in the field value and the Automation rules are not going to be triggered.

Would you be able to elaborate more on this?

Jurica Petricevic

these components are used only by automation. No user needs to do anything with them and they don't need to be seen. I use automation in such a way that when the main ticket changes the status, I create subtasks which then get this component and then belong to a certain assignee.

I just don't want those 3-6 components to be seen when creating the main ticket.

Jurica Petricevic

This is the more difficult solution than the one we currently have. For now, the project has already come to life like this. I hope to find some solution how to hide the peeled components in the jira.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

atl-gruland