Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,457,880
Community Members
 
Community Events
176
Community Groups

Jira Admin Says No

Where do you draw the line? When to put a stop to your fellow employee's crazy ideas about workflows with 100 statues or the 100th permissions scheme?

I guess the big question is: what are the best practices to saying no to a requested technical solution and how to make the requester bend a bit in order to preserve Jira's sanity and configuration simplicity?

But that's not as catchy as "Jira Admin Says No".

How do you say no? That's what I'm curious about.

0 comments

Comment

Log in or Sign up to comment