Deactivating components

[Rumceisz]

Hi All,

is it prossible to deactivate components? Which means that the users will not able to choose the component but the it won't be deleted from zhe old issues.

Thanks in advance,

Rumi

[Nic Brough -Adaptavist- · Accepted solution]

I think Rumi might be wanting to deactivate specific components - like if you've got a Sandwich project, with components ham, cheese and salad, and you run out of ham, so you want to stop people asking for it. Sadly, inactivating individual components is not yet an option (it would be very useful though, and there's a request for it somewhere)

[Rumceisz]

So there are no available workarounds for this?

If I make it readonly in the edit screen I cannot choose components at all. It would be avoided hence there are a lot of active components.

[Nic Brough -Adaptavist-]

In older versions, I've seen components disabled by the use of javascript, but that's becoming increasingly difficult and messy because fields are becoming more accessible - you used to have to code to catch the issue create and edit screens, but now, you need to deal with in-line edit, edit in popup, and all the greenhopper stuff. And javascript is a doddle to bypass, and it doesn't work over REST, so gadgets and external systems ignore it...

[Rumceisz]

ok Thanks for the info!

[James Mason]

Still not an option in 2021.   Kind of makes you wonder about Atlassian's commitment.

[Nic Brough -Adaptavist-]

Just not a lot of call for it, so it's stayed low on the list.

[Thomas Heidenreich]

You could delete the components from the edit and create screens.

[Mizan]

You will also need to make it readonly on view issue screen by turning off the inline edit .

[Thomas Heidenreich]

No, you don't as fields not present on the edit screen are not inline editable.