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

Choosing multiple components when creating a task

Stefan

Hi,

we created more than 50 components in Jira server. When we create a task we often need to select 5, 6, or more components. This process is a bit annoying. We need to open the components list box, scroll down to "show all"- > the listbox positions at line 1 again, we need to scroll down again and choose the component. This whole process need to be fully repeated for every component we want to add. If you have done this 6 or more times for every task you get annoyed if you have to create 10 or more new tasks.

Is there a better / easier way to add multiple components to a task (or subtask / bug)?

Suggestion: A listbox with the possibility to select multiple components at one would be really nice here!

Regards
Stefan

Accepted answers

Ivan Lima

Hey @Stefan , component is a renderable field. You can configure it as a select list renderer instead of autocomplete renderer (default). You can update it through your field configuration by selecting renderers and change it to select list.

Configuring renderers

Screen Shot 2020-01-03 at 1.15.39 PM.png

Cheers,

Ivan.

All comments

Alex Laycy_dvwa4f

Hi Stefan,

Are you creating similar enough tasks often enough to justify perhaps creating a template issue to clone (just be sure to remove the clone issue links afterwards), or potentially using some automation? (i.e. if issue has x in title then add x components post creation)

A 3rd workaround, again if there are commanalities between at least some of the issues, could be to use bulk edit after you've created the issues to select multiple ones and add components to each of them. Again, not ideal but perhaps a little quicker.

- Alex

Stefan

Hi Alex,

thanks for your suggestions.

A template won't fit, the components selection is in most cases too different.
An automation that is running afterwards might be able to add some components, but might also add the wrong components too (it is not trivial to choose the correct components for the current task).
Bulk edit might help a bit, but really only a little bit.

Ivan Lima

Configuring renderers

Screen Shot 2020-01-03 at 1.15.39 PM.png

Cheers,

Ivan.

Stefan

Hi Ivan,

thanks for your answer. I created my own field configuration scheme, added my own field configuration, changed the renderer for components -> and it worked fine

Thanks!

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server