Jira Admin Says No

[Krisztian Kovacs]

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.