Needs
-
Jira is the worst project manager software, except for all the others - Churchill
Having used quite a few others: hard disagree
Several companies I've worked at had bespoke internal systems that were less general but extremely efficient to use.
It kills me to think some bean counters probably gutted them and gave the money to Atlassian
-
No consultancy can ever make Jira fast. It’s incredible that it takes several seconds just to open a motherfucking goddamn issue.
I swear all their SQL is
select * from *;
wrote on last edited by [email protected]As a person who has designed several enterprise data models, I would like to personally congratulate the entire middle school class that belched up Atlassian's
-
What's a good alternative to Jira?
Once I worked at a place that had its own in-house project management software. It actually worked rather well. Part of the problem is that every company has its own process and Jira and the like try to accommodate all of them and it ends up being a jumbled mess that doesn't fit anyone's actual process. It's like trying to fit a tesseract-shaped peg into a round hole. But companies don't like to spend money on developing their own software so that's what we end up with.
-
GitHub tickets are fine.
Jira is complicated because PMs want it to do everything. It can, but there's no good reason for it.
BugZilla works for lots of usecases also
-
God, confluence is so fukcing dogshit.
I wish it wasn't. Ideally having a central knowledge base for your project with all sorts of features sounds amazing.
Then you get confluence, where loading a si gle page somehow takes 7 seconds, and your documentation is split among dozens of pages each if which take equally as long or longer to load.
Folders take like 3-4 seconds to unfold and reveal what documents are inside.
It's such a piece of shit
Remember open source wikis? Twiki?
They were much better. More functional, faster, intuitive.
Corporates got rid of those and Atlassian got rich
-
I was a vocal hater of Jira till I switched to a company that rolled their own ticketing system. Now I love Jira.
I had the opposite experience.
Some in house devs are extremely talented and have (middle) management support.(Upper management fires those groups and uses the savings to buy Atlassian)
-
Teams is trash, I have to use it with certain clients, slack for everything else. Literally everything it does is like a wish.com fail version of slack. Like if you ordered slack on temu.
Worse than Slack...
Now that is saying something
-
This post did not contain any content.
Fuck. Monday is tomorrow. I go back to this shit, and pretending to care about my job...
-
What's a good alternative to Jira?
Probably controversial, but I like Notion for this.
it's easy to customize properties, moving issues around is smooth, and writing inside a page feels natural to me.
-
I would prefer Jira over ServiceNow, my previous job had jira and it ran smooth, ServiceNow is just a clunky mess
Bit unpopular, but I actually prefer servicenows ticketing system over Jira. Although a big part of that comes down to how my team worked for a while
For a while I had to use Jira for any cloud work and ServiceNow for any dev work on that platform. Keeping track of 2 different boards is maddening
-
There's an appropriate time and place for any methodology. There's never an appropriate time or place for Teams or Jira.
There's no appropriate time or place for Scrum or any other "agile" methodology that has a name.
There may be some appropriate usage for some methodology your team creates in a meeting. Never for those pre-packaged ones.
-
This post did not contain any content.
I actually like Jira. I have my own workflow where I fetch my tickets via Emacs to Orgmode and then work from there. Integration is read-only but that is what I need 99% of the time.
-
You're not responsible for anything. I'm just saying if you only require that Windows makes its apps compatible with iOS and smooth, you should require the same from Apple with regards to Windows. It's a two-way street.
wrote on last edited by [email protected]I never said it shouldn’t be the other way around too, why would I need to? Should I mention everything that is going wrong in this world when I’m talking about one thing?
-
I would prefer Jira over ServiceNow, my previous job had jira and it ran smooth, ServiceNow is just a clunky mess
I were unfortunate enough to get an assignment about sending messages to ServiceNow through a REST interface. The company had a team that managed ServiceNow, so I set up a meeting with one of the people there to get read access to the test environment so I could confirm that it worked. The person invited, then invited a coworker who in turn invited the manager of their department. During the meeting we got established how little they wanted my team to do anything that could affect the system due to how easy it was to make mistakes that took weeks or months to fix, how complicated it was and how many years it took to be proficient in. The whole thing was basically a lecture on how unequiped our team was to manage their system and how they didn’t want us to break it with changes we weren’t planning on making anyway. It took a few meetings after that to get credentials and when I got them I got admin access for some reason.
That experience left me wondering why ServiceNow was even being used as it sounded like a liability more than anything else. -
next time my job asks me to install teams on my phone, I'm gonna hand them a list of rental costs for access to my phone/internet and to cover any security related issues.
I'm fine with it, since they pay my phone bill if I have it installed ¯\_(ツ)_/¯
-
Where is "slapping management insistent on AI?"
wrote on last edited by [email protected]Ah man, my boss wants to get our department Meta glasses for taking pictures of parts we make, we literally get a bonus on our pay cheques for us having our phones on us an be reachable.
-
I actually like Jira. I have my own workflow where I fetch my tickets via Emacs to Orgmode and then work from there. Integration is read-only but that is what I need 99% of the time.
Jira is so much better than the new programs introduced in the last few months. Almost everything could be done on a Jira ticket before. Now I need to go to Jizz for a work order, Bellow for an off the shelf inventory addition, GroupCenter for releasing a drawing, and SimpSupport for IT help. It's like an MBA in upper management pushed these additions and then fucked off as soon as they started implementing them before it blew up in their faces. Off to search for the next company's productivity flow to ruin.
-
and it does so for abso-fucking-lutely no good reason!
Vendor lock-in. The next generation will demand teams because they cannot get used to other shortcuts.
i mean...that certainly is an explanation, but it's a shit strategy:
there are a lot of objectively false names for emojis, you can't expect people to get used to that...
"eyeroll" for example is called "bored"...which makes absolutely no sense. (at least in german, maybe it's less bad in english)
I don't see that ever leading to vendor lock-in, just perpetual frustration...
-
Having used quite a few others: hard disagree
Several companies I've worked at had bespoke internal systems that were less general but extremely efficient to use.
It kills me to think some bean counters probably gutted them and gave the money to Atlassian
Hell, my employer used to just have us turn in Excel-based at the end of each week. They were super easy and fast to fill out. After the switch to Jira it takes 3x longer.
-
I were unfortunate enough to get an assignment about sending messages to ServiceNow through a REST interface. The company had a team that managed ServiceNow, so I set up a meeting with one of the people there to get read access to the test environment so I could confirm that it worked. The person invited, then invited a coworker who in turn invited the manager of their department. During the meeting we got established how little they wanted my team to do anything that could affect the system due to how easy it was to make mistakes that took weeks or months to fix, how complicated it was and how many years it took to be proficient in. The whole thing was basically a lecture on how unequiped our team was to manage their system and how they didn’t want us to break it with changes we weren’t planning on making anyway. It took a few meetings after that to get credentials and when I got them I got admin access for some reason.
That experience left me wondering why ServiceNow was even being used as it sounded like a liability more than anything else.Yeah that sounds about right, the ServiceNow config at my work also feels like a house of cards, I also feel like I lose at least an hour of work anytime I have to interact with the damn thing