I’m curious to learn from real experiences sometimes, even a minor tweak like a workflow update, automation rule, or field change can significantly improve efficiency. In your case, what’s that one change that actually made day-to-day work smoother for your team? Would love to hear practical examples that delivered real value.
@Yashodip Jadhav A couple of things I've noticed over time:
I mean, this does sound like a classic marketing pitch 😅, but indeed, some things can be really improved if you put a decent amount of time into detecting some issues within the process.
We also encourage users/clients to talk with their power users and gather ideas of what can be improved 👀
Hello @Yashodip Jadhav ,
First Welcome to the community !
One small change that had a big impact for our team was simplifying the workflow we reduced unnecessary statuses and focus on the key steps
At the same time we added a bit of automation to handle transitions and field updates in the Background.
This made the workflow clearer and reduced confusion about "where things should go" .
Another tips , we implement the automation rule for repetitive actions that reduce the manual effort , minimized human errors and save time .
We also improved how we use the work item linking by encouraging teams to link related work this gave much better visibility and understand relationships between work items clearly .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello and Welcome @Yashodip Jadhav
For me, one small change with a big impact was cleaning up the create screen.
We reduced the number of fields users had to fill in when creating an issue and kept only what was really needed at that moment. Everything else was either handled later in the workflow or filled through automation.
That sounds minor, but it usually has a very real effect. People create tickets faster, they make fewer mistakes, and the overall quality of incoming issues often improves because users are not blocked by too many required fields.
In my experience, one of the best Jira improvements is often not adding more, but removing friction.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.