Community resources
Community resources
Community resources
- Community
- Tag: worst-jira-admin-contest
Tag: "worst-jira-admin-contest"
-
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...
-
Mistake 3 (Remedy) In a previous article in this series called “Worst Jira Admin Contest: A Hundred Issue Types“ I shared the story of a company that had 134 issue types and many unnecessary issue ...
-
Mistake 19 One day a former employee contacted the company to complain about Jira data being sent to their personal email address. Upon investigation, I discovered that data was being sent to hundr...
-
Mistake 18 How are your global groups and external user accounts structured? You need a specific way to handle external consultants, vendors, auditors, and even interns or temporary employees. Co...
-
Mistake 17 For today’s tale of security horror, I’ll share the story of a small company that had Jira Server and used Atlassian’s Crowd product to store user credentials. Their tools were public...
-
Mistake 16 I recommend not creating more than one custom field with the same name. Even if the fields have different types, it makes it hard to differentiate between them. It’s hard to tell the dif...
-
Mistake 15 The title “Worst Jira Project Admin” is more appropriate for this mistake I experienced. The IT support team uses the Jira “components” field to categorize which application or...
-
Mistake 14 Here’s a recent one that I’m not proud of. I was helping a client delete unneeded custom fields from their Jira Cloud application. We followed my usual custom field clean-up procedure wh...
-
Mistake 13 Ses·qui·pe·da·lian - having many syllables, characterized by the use of long words How long should a Jira project key be? While a long key is allowed in Jira, it makes little ...
-
Mistake 12 How many application administrators should an application have? At one company, there were 132! There were no procedures to determine who was eligible for application-level admin ...
-
Mistake 11 Have you ever wasted time using the wrong information? Are users requesting to add incompatible apps? Are you getting config advice from ChatGPT? Here’s what you need to know: Correct ...
-
Mistake 10 When you’re wading through mucky configurations, you never know what is lurking underneath. Seemingly simple clean up activities are more complex or dangerous then they initially seem. I...
-
Mistake 9 I know I’m not the only one who’s made this mistake! I once changed a status in the “diagram” workflow editor. I thought I was swapping one status for another and that the change wou...
-
Mistake 8 Sometimes workflows break or develop conflicts due to administrative actions in other areas of Jira. In Server and Data Center, the built-in Integrity Checker function can sometimes detec...
-
Mistake 7 Do your users keep Jira issue status in sync with reality? In my experience, they do not. Issues are often forgotten about in certain statuses. Does this happen in your application? Then,...
-
Mistake 6 “Someone get this kid admin access!” - Rachel Wright with her Commodore 64 My first admin experience was on the day I was made an application administrator! (Not ideal!) I had a v...
-
Mistake 5 Having a test environment is a good start, but it’s not enough. Have you ever thought you were in a test environment but were actually in production by mistake? Never happens, right? 😉 A...
-
Mistake 4 It’s shocking, but many organizations don’t have a test environment! I didn’t have one when I first started out either. But I quickly saw how important it was to be able to experimen...
-
Mistake 3 How many different issue types and combinations of issue types could one organization possibly need? One company had 134 issue types and many unnecessary issue type schemes! Thi...
-
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 did ...
-
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 learned...
-
“Oops!” “Oops! I can’t believe I did that!” “Oops! I can’t believe I did that in PRODUCTION!” Remember that time you prevented everyone’s progress after a permission change? Or the time yo...
Copied to clipboard
