askchapo

There are a million ways to use jira and most of them suck. Still, it's possible for jira to be a great tool as long as you focus on the question "what problem is this new workflow solving?"

Jira can be an excellent tool for communication and managing workload expectations

Not sure why you spelled it that way but gyros are succulent greek dishes that you can enjoy with almost any kind of condiment. Think your sales will go up if they are used at work to make meals, congrats

It will be a little annoying to use at first, then pretty helpful because it is full-featured and keeps track of things you need to know, then over the next 1-2 years your managers will slowly start using its stats to judge everything you do, and over the next 2-3 years your company will slowly grow a class of project managers who exist to add more convoluted processes that you have to follow on Jira before doing anything.

i mean it really is about how its utilised and what addons are used. I seen it go from a nice bugreporting and project management tool to a glorified timetracker.

It really depends on how your board owner configures it. Jira can do nearly nothing or it can have an immense amount of restrictions and automation and notifications. It's up to the board owner how much it helps you work vs how much it gets in the way of your work. If there's something you think you'd like it to do, find your jira admin or expert and ask them....it probably can, if the admin knows how to make it.

The only thing I can guarantee with Jira is that the moment you get used to a workflow or a process, someone, including and especially atlasian, will change it. Then you get to learn it all over again. So look forward to that.

I don't think it will really make much difference. Ive been on dev teams who use Jira, and even do all of the agile ceremonies, but are still super chill. If you're management is ok now it will probably stay that way.

Also most devs seem to be illiterate and can't write more than 3 sentences at a time. So when you write stories you can get tons of praise from everyone just be writing a couple of paragraphs that actually describe the problem.

what tracker are you using now? Jira is better than Trello for large projects, and better than Hansoft because it has a clearer workflow.

Trello is much better for small projects with only a few developers though.

but that's just, like, my opinion. I've worked with Jira for almost 10 years so I'm biased.

if there is agile brainrot in your organization, expect it to continue, I'd say. if you already have people hassling you about story points and epics now, it'll be about the same. if not - buckle up, they might get encouraged.

producers and other project people love Jira but so does QA, and as a dev I want QA to thrive so I'll take the good with the bad.

We use Jira at my job. It sucks because time management suck but other than that it is a decent tool for structuring the tasks in a project. It all depends on how your project management uses it. If they are trying to micromanage you and strangle you in red tape, Jira absolutely allows them to do so but if they are interesting in getting things done Jira is also good at that.

It can get a lot worse than Jira though. When my old job got bought up by some big fancy software firm we were switched from Jira to some Microsoft solution that was probably decent enough but it was annoyingly Microsoft-y and it was integrated with an absolutely cursed third party time tracking app whose buggy turn-of-the-milennium UI made timesheet red tape a daily nightmare. Switching jobs and going back to Jira (and a less anal project management culture) was a huge relief.

Jira's a pretty good tool, but I've never used any other issue tracker in my decade plus as a dev.

You will lose PMs to the process whereby they transform into creatures that live entirely on Jira.

We use it at work and it's okay. But I'm not a Dev so I don't know how it will be for you

JIRA is fine as a organizational tool, the problem how it's applied and abused by management. The second you get some project manager sharing their screen with the entire dev team to go over "burndown" and talk about "velocity" you can safely zone out, unless there is a serious effort by management to couple metrics like "JIRA ticket points completed" to individual (or even team) performance.

Especially if that last point becomes true, consider this a good opportunity to apply this handy guide. Bouncing back requests with "please create a ticket" or "please make sure this ticket is assigned to the right epic" or whatever hairs you can split is a great way to get nothing done while also giving the appearance that you're somehow actually doing work. Most managers are already just pushing virtual papers around, so they are often completely blind to devs doing the same with systems like JIRA.

I'm at the end stage of Jira mentality which about 6 years ago started as self run agile teams using it for tracking to help with estimates and organise teams.

Now we're running a skeleton crew where my daily job which was once software engineering is now ticket engineering with 9-5 meetings every day and micromanagement of a degree I'd expect from a factory line where all i do is write tickets for faceless offshore contractors i won't ever meet who work on those tickets.

It's very dependent on the actual culture of your workplace for a few places I've worked at it didn't really change anything but it can get really bad if the powers that be figure out how to use it as a cudgel to wring you dry.

I like Jira itself. What's negative about it is requirements are hard and most scrum masters and whoever will be writing your tickets suck at it. The problem is getting good at establishing requirements and putting that into text. But as for Jira itself, it's brilliant.