Don’t Be a Slave to Jira

If you’re a developer, you’ve probably come across Jira. If you’re working with Jira right now, you probably know the pain.

You pick up a task. You move its ticket into “In Progress”.

You raise a pull request (PR). You move the ticket to “Code Review”.

Your PR is merged. You move the ticket to the “QA column”.

And you need to remember to follow these steps for every task. There is no reason. We have workflow triggers. You can configure your workflow so that tickets move automatically based on certain events. A PR is created? Move the ticket. A PR is rejected? Move the ticket. A PR is merged? Move the ticket. You get the idea.

Even if you don’t manage your Jira board, get whoever manages it to set up workflow triggers. It’s a huge time saver. It also improves the accuracy of your Jira board.

If you’re using other project tracking software, look for a similar feature. It is probably there.

Save some time. Spend it on something more productive than moving tickets around.

Published by eranboudjnah

A software consultant and tech lead. Passionate about optimizing as many aspects of my life as possible, to free time for what really matters.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: