I submitted a ticket in Jira Support to report a bug and coincidentally encountered another bug that prevented my ticket submission from going through. So now I have to make a ticket for my ticket, right?
Spent an hour updating a story, wrote 10 items with screen shots and all.
JIRA decided to revert to an old version and did not save anything to the change history.
It’s wild how much time we burn explaining Jira to new devs instead of onboarding them to the actual product we’re building.
I’m all for flexibility, but when your PM tool needs its own specialist, it’s probably not a dev tool anymore. For a while, we even had a dedicated person whose whole job was just to manage our Jira setup and clean up unused workflows.
These days we’re on Monday Dev. The setup took an afternoon, and it hasn’t really needed maintenance since. It’s not trying to replace Jira one-to-one, but it does the 80% we need without 200 dropdowns and a dashboard that looks like a cockpit.
The thing about jira is it attracts spreadsheet bureaucrats. Everything was fine in azure devops but a bunch of people were complaining about not being able to datamine it. So we switched to jira and suddenly we were getting questions about why a ticket lived longer than a sprint and why when they sum our fibonacci story points their graph doesn't look right.
I hate story points. It’s always the same arguments - “how many hours is a point”, “points don’t associate to hours!”
Except they totally do, just avoid the hidden thoughts and use t shirt sizing or engineering hours.
I find generic “hours” work best - if someone consistently overestimates lower their hours per week. If someone underestimates - does this ever happen? Assign them more hours per week. Just don’t report overall team hours if you can. It’s just metric to determine how much you can do and you can tweak it individually.
What does 'estimate correctly' mean? An estimate is always correct in the context in which it was made. If you find out more information, you can re-estimate. Any estimate is just that - an estimate - and is based on information you had at the time. Its not a promise.
Your problem is not Jira. Your problem is you don't know how to run it, change is hard for humans and you probably have no say in how it should be set up. Typical ass hat situation that get the blame offloaded to Jira.
Jira is a great program if you know how to customize it. We use it, and we love it, but not because it was born great. You have to make it what you want it to be based on use case, feedback and automations.
I hate Jira. Azure DevOps gets a bad rap but it was so ple, intuitive and did everything you needed. Jira is hateful. Why the fuck can I not simply filter by sprint? Why is it almost impossible to see past sprints? Why can I not get a list view of the current sprint and filter by the status column? My last place and current one use it and I just can't understand why. It just makes my life much harder than it should be
I had a team leader that decided "enough is enough" and forced us to use Asana and update Jira back to satisfy management... Did you ever to resort to something similar?
Sadly not. I was made redundant and got a job in a different company that uses...Jira. they're too invested in it now (switched from on prem to cloud just before I joined) so even though we are actually planning to migrate carefully from majority on prem systems to Azure, I doubt they will move to AzDo or anything else. Shame, but you have to work with what you have sometimes. I still hate Jira.
I'm sorry to hear... I actually work on AzDo now, and I find myself banging my head against the wall when handling tickets. I've found that usually these systems are actual quite alright, it's the people who own it that turn it into shit (granted, Jira has this greedy ecosystem model where you need to pay an absurd amount of money every month per user to get half decent reports like eazyBI).
I wrote some automation that helps me focus on what I want/need and let the bot fill in the gaps that make management happy. I wonder if people would even consider using it. Or do you care more about navigating Jira rather then creating/modifying tickets?
Bit of both really. I dislike a lot about Jira, the UI is nasty, not being able to see past sprints easily infuriates me, and it just seems to glitch a lot. But it's in the hand of the product team so there's nothing I can do about it. I've never liked Jira, even 15 years ago when I had control of it 😂
"Jira, where productivity goes to die. Don't worry, we feel your pain! Maybe take a deep breath, grab a snack, and try to find the one ticket you actually need to work on. #SmythOS AI Agent feels your Jira struggle"
We do the same, and our company has a huge Jira installation. Our team of 8 people have to sit and wait everytime a ticket needs to be added to an Epic because Jira looks at all the epics. It's like a solid thirty seconds everytime. These slow downs eat up so much time if it was all added together. But generally, it gets the job done. Just wish it was faster and less cluttered.
Confluence needs to be shot and left for dead behind the barn.
I worked 11 years with TFS/ADO for the same customer in an argentinean Consulting Firm. Suddenly after 10 years an auditor asks me why I don't use Jira, which is the company standard. Simple I said, I use the customer tools. You need me to do something new? Just ask for it. This is how atrocious a tech job has become. Total disconnect with reality.
So, I recently joined a company that refuses to use JIRA. They built their own task management app (that is still very rudimentary) along with a slew of other productivity applications.
I have just joined them as a Product Manager and I am learning the ropes here. As I begin to take on and start building out the application, I was hoping to get some feedback on it's current state to shape its future.
Should any of you have the time and want to participate in building out the tool, HMU or use the link https://appointly.innoscripta.com/hassan-advani-active-times
If you find the platform useful, your organisation can use it free of cost.
Jira went from being developed for a specific use-case to being developed to be a crappy key value store with a UI that looks like it's managing data well, but the reality is:
It lets you overwrite data.
Doesn't allow for multiple users editing a single field
Workflow has been converted to a giant "workflow engine" that's so customizable you can't really figure out how to work it
It doesn't need access control, but it does, even though it's replacing cards on a board
History of ticket is horrible (see but not restore)
i was a JIRA proponent... for years.. then it started to go against itself - like REJECTING comments or content pasted into it.. because of some formatting thing.. WTF?
I was super fast in using it.. then update after update.. made it a fight to use it
Currently, I'm fighting daily w Confluence aka Satans Wiki (hilarious).. it reminds me of Word 1998.. fighting that piece of goodness to make a basic doc layout..
UGH. Tools people! Why are the tools making a tool out of me?
#lameaf
rant now completed. blood pressure back to normal. #woosah
Its to do with my personality type, i prefer to be unorganized and take things as they come instead of having an endless list of tasks to complete and people chasing me for things. Feel like i am being watched, the tool isn't being used as a dev tool its all about tracking performance
Rare_Year_2818@reddit
I test beta software for a living and Jira is still some of the least intuitive UX I've ever encountered
r1ckd33zy@reddit
Take a ticket and join the line...
Rare_Year_2818@reddit
I submitted a ticket in Jira Support to report a bug and coincidentally encountered another bug that prevented my ticket submission from going through. So now I have to make a ticket for my ticket, right?
Vetali89@reddit
Jira is still shit and slow AF even on the 9800X CPU !
Fuck you Jira ! But I have to use this shit because the company uses it.
serg3e@reddit
Spent an hour updating a story, wrote 10 items with screen shots and all.
JIRA decided to revert to an old version and did not save anything to the change history.
F*** JIRA!
mfb1274@reddit
You fucking hate the way your company uses Jira
breadlygames@reddit
A bad toolmaker blames his users.
g9icy@reddit
I hate Teams. No really... I HATE Teams.
Antique-Set-1404@reddit
EVERYONE hates Teams
itshammocktime@reddit
I like jira *shrug* . Requires a well run instance and PMs not putting too much structure in place though
Antique-Set-1404@reddit
thats just it. PMs always put to much. A smart system would preclude such activity
saucetinonuuu@reddit
I’m 2 years late to say Jira fucking blows.
ufrontenddog@reddit
It’s wild how much time we burn explaining Jira to new devs instead of onboarding them to the actual product we’re building.
I’m all for flexibility, but when your PM tool needs its own specialist, it’s probably not a dev tool anymore. For a while, we even had a dedicated person whose whole job was just to manage our Jira setup and clean up unused workflows.
These days we’re on Monday Dev. The setup took an afternoon, and it hasn’t really needed maintenance since. It’s not trying to replace Jira one-to-one, but it does the 80% we need without 200 dropdowns and a dashboard that looks like a cockpit.
EmergencyOk6673@reddit
wowwwww
fixermark@reddit
Jira sucks because it violates the first rule of software UI design: "Thou shalt not destory user data without an undo or a warning."
Convert an epic with stories attached to a story, and your child stories scatter to the four winds. That's just bad software design, period.
Sofmen_Joel@reddit
Check out https://taskboard.dev/; it is a lot easier to use than JIRA. Full disclosure: We built it after using JIRA and other tools.
Usual_Watercress1263@reddit
I hate you
Worth_Trust_3825@reddit
tldr: my jira is configured by people not in the process.
Complex-Somewhere413@reddit
Yes! I fucking hate the Jira Admins at my company!
dfwtexn@reddit
I live this reality, daily.
Antique-Set-1404@reddit
Same here unfortunately
noy-g@reddit
And you're not in a position to do anything about it? Or do the Jira owners refuse to hear anyone's opinion other than theirs?
Johnothy_Cumquat@reddit
The thing about jira is it attracts spreadsheet bureaucrats. Everything was fine in azure devops but a bunch of people were complaining about not being able to datamine it. So we switched to jira and suddenly we were getting questions about why a ticket lived longer than a sprint and why when they sum our fibonacci story points their graph doesn't look right.
I don't work at that company anymore.
SaltwaterOcean@reddit
Fibonacci story points are shit. No producer (who is tracking against budgets) can possibly think they're a good thing. It's all hype-dribble.
JB-from-ATL@reddit
"Story points can't be used to compare across teams. They are not time estimates and vary team to team."
Then
"Why does this team not accomplish as many story points? Are they slacking? Is there a problem?"
goomyman@reddit
I hate story points. It’s always the same arguments - “how many hours is a point”, “points don’t associate to hours!”
Except they totally do, just avoid the hidden thoughts and use t shirt sizing or engineering hours.
I find generic “hours” work best - if someone consistently overestimates lower their hours per week. If someone underestimates - does this ever happen? Assign them more hours per week. Just don’t report overall team hours if you can. It’s just metric to determine how much you can do and you can tweak it individually.
pojzon_poe@reddit
If I had 5 clones of me in the team I could estimate pretty correctly.
When team represents different seniority its impossible to estimate correctly or even guesstimate.
For one person it can be 5h for another it can be 5days lol.
goomyman@reddit
I doubt that. I can’t estimate my own work correctly.
Well I can but 90% of the time your asked to estimate the unknown. You can be very accurate on a codebase you already understand with clear asks.
p3365@reddit
What does 'estimate correctly' mean? An estimate is always correct in the context in which it was made. If you find out more information, you can re-estimate. Any estimate is just that - an estimate - and is based on information you had at the time. Its not a promise.
goomyman@reddit
Management wants dates. Which makes sense. You pick a date up front.
To meet that date usually it involves cutting features first than reestimating.
fnord123@reddit
Ironically I manage my projects in spreadsheets because jira is too slow and search eats shit.
Far_Percentage_7460@reddit
Man, spreadsheets are the worst. Couldn't imagine working under you, i'd hate it and probably leave!
fnord123@reddit
It's basically just a list of tickets I'm interested in, links, and their statuses.
Devildawq1@reddit
Why not?
Turbulent_King4164@reddit
Your problem is not Jira. Your problem is you don't know how to run it, change is hard for humans and you probably have no say in how it should be set up. Typical ass hat situation that get the blame offloaded to Jira.
Jira is a great program if you know how to customize it. We use it, and we love it, but not because it was born great. You have to make it what you want it to be based on use case, feedback and automations.
CompetitionDry1321@reddit
The worst software service I've ever used. Impossibly stupid.
WinAvailable9561@reddit
To create a 1 line issue i need to fill at least 10 useless fields
BitterOtter@reddit
I hate Jira. Azure DevOps gets a bad rap but it was so ple, intuitive and did everything you needed. Jira is hateful. Why the fuck can I not simply filter by sprint? Why is it almost impossible to see past sprints? Why can I not get a list view of the current sprint and filter by the status column? My last place and current one use it and I just can't understand why. It just makes my life much harder than it should be
noy-g@reddit
I had a team leader that decided "enough is enough" and forced us to use Asana and update Jira back to satisfy management... Did you ever to resort to something similar?
BitterOtter@reddit
Sadly not. I was made redundant and got a job in a different company that uses...Jira. they're too invested in it now (switched from on prem to cloud just before I joined) so even though we are actually planning to migrate carefully from majority on prem systems to Azure, I doubt they will move to AzDo or anything else. Shame, but you have to work with what you have sometimes. I still hate Jira.
noy-g@reddit
I'm sorry to hear... I actually work on AzDo now, and I find myself banging my head against the wall when handling tickets. I've found that usually these systems are actual quite alright, it's the people who own it that turn it into shit (granted, Jira has this greedy ecosystem model where you need to pay an absurd amount of money every month per user to get half decent reports like eazyBI).
I wrote some automation that helps me focus on what I want/need and let the bot fill in the gaps that make management happy. I wonder if people would even consider using it. Or do you care more about navigating Jira rather then creating/modifying tickets?
BitterOtter@reddit
Bit of both really. I dislike a lot about Jira, the UI is nasty, not being able to see past sprints easily infuriates me, and it just seems to glitch a lot. But it's in the hand of the product team so there's nothing I can do about it. I've never liked Jira, even 15 years ago when I had control of it 😂
Ok-Opinion4633@reddit
"Jira, where productivity goes to die. Don't worry, we feel your pain! Maybe take a deep breath, grab a snack, and try to find the one ticket you actually need to work on. #SmythOS AI Agent feels your Jira struggle"
SaltwaterOcean@reddit
"You want a new workflow? Sure, here's 100 steps that make no sense."
SaltwaterOcean@reddit
Agreed. Most convoluted piece of software ever invented.
incrediblynormalpers@reddit
Recently learn today how f****** bad jira is how much of af****** mess their UI is.
Nocty3248@reddit
It still sucks in 2024 FYI
aleques-itj@reddit
I dunno we basically use the Kanban board and run over tickets in a stand up every few days.
Things move along and things get built so I guess it works fine.
deleted_by_reddit@reddit
We do the same, and our company has a huge Jira installation. Our team of 8 people have to sit and wait everytime a ticket needs to be added to an Epic because Jira looks at all the epics. It's like a solid thirty seconds everytime. These slow downs eat up so much time if it was all added together. But generally, it gets the job done. Just wish it was faster and less cluttered.
Confluence needs to be shot and left for dead behind the barn.
sudomatrix@reddit
30 seconds is enough time for my ADHD to make me go do something else. I won't return to finish the Jira ticket for another 4 hours.
MaintenanceSuper2251@reddit
I worked 11 years with TFS/ADO for the same customer in an argentinean Consulting Firm. Suddenly after 10 years an auditor asks me why I don't use Jira, which is the company standard. Simple I said, I use the customer tools. You need me to do something new? Just ask for it. This is how atrocious a tech job has become. Total disconnect with reality.
leon_PMI@reddit
So, I recently joined a company that refuses to use JIRA. They built their own task management app (that is still very rudimentary) along with a slew of other productivity applications.
I have just joined them as a Product Manager and I am learning the ropes here. As I begin to take on and start building out the application, I was hoping to get some feedback on it's current state to shape its future.
Should any of you have the time and want to participate in building out the tool, HMU or use the link https://appointly.innoscripta.com/hassan-advani-active-times
If you find the platform useful, your organisation can use it free of cost.
coding2017@reddit
Jira went from being developed for a specific use-case to being developed to be a crappy key value store with a UI that looks like it's managing data well, but the reality is:
Repulsive-Ad-7503@reddit
I've recently even written an article on that topic. But more in a diplomatic manner:)
dead_ed@reddit
Jira is not fucking useful. It works against you at every turn.
ctoxyz@reddit
i was a JIRA proponent... for years.. then it started to go against itself - like REJECTING comments or content pasted into it.. because of some formatting thing.. WTF?
I was super fast in using it.. then update after update.. made it a fight to use it
Currently, I'm fighting daily w Confluence aka Satans Wiki (hilarious).. it reminds me of Word 1998.. fighting that piece of goodness to make a basic doc layout..
UGH. Tools people! Why are the tools making a tool out of me?
#lameaf
rant now completed. blood pressure back to normal. #woosah
Far_Percentage_7460@reddit
Its to do with my personality type, i prefer to be unorganized and take things as they come instead of having an endless list of tasks to complete and people chasing me for things. Feel like i am being watched, the tool isn't being used as a dev tool its all about tracking performance