...nd improve over time. Let’s confess our admin mistakes, talk about what happened, and why. Join this informal contest to see who can top my mistakes and win the prestigious title of Worst Jira Admin...
...undreds of other past or present users with external addresses in the Jira database. There were two problems: former users weren’t being deactivated and external email addresses were a...
...hen, read on! Admin > Issues > Statuses Status Categories In Jira, statuses are classified into one of three categories: “To Do”, “In Progress”, or “Done”. In modern versions of Jira, “T...
Mistake 20 One day I was building a Jira Cloud automation rule to show an example of using smart values in one of my Jira courses. The purpose of the rule was to send an email to an external user w...
...eserves? Do the admins for "all the other apps" understand the specifics of Jira administration? Instead, form a dedicated team of admins who actually LIKE and care about the application! Back to i...
Mistake 1 One of the worst workflows I’ve seen is unfortunately, one I built. We were having process problems and thought a comprehensive Jira workflow would solve them. But I’ve since l...
...irst Jira project, I followed this flawed model and instead of leveraging existing issue types like “Feature”, “Bug”, and “Task”, I created more custom options like “Technology Feature”, “Technology B...
...ittle sense to make end users type something too long. Jira project names and project keys are critical attributes to help identify projects and issues. A best practice is to make the project's t...
Mistake 2 As a Jira administrator and consultant, I’ve seen plenty of horrendous workflows. The worst had 39 statuses and 1,007 transitions. It’s the longest workflow I’ve seen. And no, I d...
...onsider the following use cases: 2 external users from “Alpha” company need access to the X Jira project 3 external users from “Bravo” company need access to the Y Jira project 4 temporary c...
Copied to clipboard