Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Jira. In the Software-as-a-Service world, it's often the tool of choice by Product teams to track issues, by breaking everything down into stories.
It's a horrible, slow, janky mess. The interface is confusing and poorly laid out, you can easily have too many options all over the place, and how its even used can vary dramatically from one company to another.
Salesforce is also trash for very similar reasons. How Sales people around the world all vouched for this thing is beyond me.
Can confirm JIRA is an unusable mess. Submitting IT tickets was probably the worst thing about my last job. So much time wasted filling out irrelevant fields of information.
Of course, while I'll agree about Jira being unfortunate, I'll say from experience it's the "committee" of people that end up making up tons of fields imagining that they have some utility. Jira is complicit by saying "sure thing, as many required and cross-linked fields as you like!"
We have "Priority", "Severity", "Importance" on top of the sort order having some other indication of relative importance, all must be filled. Opening an item in one place requires you to have an item already opened in another place and that one requires a project id from some other tool to know who to charge, in theory. In practice it's not hooked into any charging system, but they imagine one day departments can charge each other for fixing items. We also have about 4 additional "describe the ticket" fields and in addition to the title, there's a 'One line summary'. All required.
I guess we just use a very stripped down version of jira, because it's really just enter an issue, brief explanation, and further documentation to help whoever comes to fix it solve it faster. If it takes me longer than 5 minutes to create a ticket that means I've spent way longer than usual.
I think of it as a good place to keep a record of know issues or desired improvements, so they don't get forgotten.
The worst thing about it is when you're trying to move the tickets around. If you assign a ticket to another team the software then drops you into their queue, because I definitely want that to happen.
I think it's just an issue with the browser caching getting messed up because it doesn't use the proper version history API
what do you consider a good alternative?
Fwiw their zephyr plugin is pretty good imo
What would you recommend instead?
The sole purpose of jira is to create a shiny thing to distract PMs so they don't bother the engineers too much.
Jira doesn't suck, your management does