Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Hide unused add ons

Looking at our issue screens every screen shows the various 3rd party add ons that we subscribe to. Some of the projects don't need to see various 3rd party options. Is there a way to hide add ons from various issue screens?

1 answer

0 votes

No, because they might be used.

That's a short sighted approach. We have a quoting add on that we use in our sales project. I can guarantee that nobody who is working our dev projects will ever need to use the quoting add on. There should be an ability to hide any item when creating an issue screen.

So how is it "short sighted" to let people use functions they may need or benefit from?

I don't see how it's worth spending time coding for, and then having admins have to set up flags for "hide", when "if you don't need it, don't click it" covers the case.

Flexibility in configuration. Why do I need teams to see functionality they will never use. I'd rather use the screen real estate for things they use.

Or you could let them see stuff they might want to use and not have to think about having to remove it because (you may well be guessing) they don't?

Don't get me wrong, I don't think there's anything wrong with people, or maybe the project lead being able to say "I don't want to see this", but you've then got a mass of code to write to enable that, and on top of it you also need to think about "someone else in this project has used it, so I'm now missing information".  It certainly shouldn't be up to an admin to be worrying about it, because they would then need to be talking to every project or even user to establish what the flags should be set to.

It's a lot less work to simply say "if you don't use it, don't click on it"

Yes, but there is so much that is configurable, it's like stopping 10 ft before the finish line. I can guarantee 100% that my dev team will never need to do a quote and our sales people don't ever use the work timers. In the configuration screens I should be able to slide any thing over to hidden (with the exception of the required fields for the issue to work).

It's not available and with the backlog of things the Jira team needs to work on this will probably never be considered, but it would be a nice feature. Let us design our screens exactly how we want so they are the most efficient for the users.

Suggest an answer

Log in or Sign up to answer
Site Admin

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you