this post was submitted on 16 Aug 2023
45 points (86.9% liked)
Programming
17354 readers
454 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
JIRA is just an issue tracker. Whatever they're doing to you with it is not its fault. ๐ You're supposed to use it to document and assign work items (stories, tasks, bugs). What has to be done, progress, duration estimates (in days!), attach whatever extra info is needed (links, files) and use the comments to keep each other in the loop and clear obstacles (blockers, dependencies etc.) It's fairly straightforward when used correctly.
You have to have some way of tracking development. If it weren't JIRA it would be something else โ but JIRA is commonly used because it's flexible and can adapt to many ways of doing things and to lots of the aspects of software development.
Nope, I mean at it's core, yes it is, but it's used for sooooooo much more than that. It enables management from a far fistance, and that disencentivices managers from doing their job.
I get the premise, that tools just exist and it's us that put our own biases in them. But that looses a lot of nuance when a tool is specifically built for a purpose, such as oversight, tracking, and data collection. These design decisions take an "issue tracker" far away from what Trello, or a whiteboard with stickies on it for that matter, does.
It is a grave mistake to think that it's just an issue tracker, and that's all it can be. I've been in this industry long enough not to fall for that con. And it is a con, when someone manipulates you using a tool that is designed to make manipulation easier (I'M not telling you to point every story even if it doesn't make sense. But you know... Jira wants it, it's just... Outa my hands...).
Nah, Jira is for managers, not developers, and is far more than a simple issue tracker.