1, Utilizing JIRA feedback as an e mail alternative
If you end up studying JIRA feedback and are available throughout issues like “Hello, how are you?” or “Sort regards, Jeremy Protect” you possibly can all the time inform the person is utilizing JIRA as a substitute of e mail. And even worse “BTW, John did not present up at work at the moment once more. Are you able to consider it?“
Keep in mind
Each JIRA ticket has its objective of finishing given job. Any data that’s not associated to duties at hand decreases productiveness. If you wish to have the duty resolved, keep targeted.
2, Not utilizing mentions
There’s a good motive Atlassian consists of this operate,.Use it! Except you might be speaking to your self Even in case you are speaking to your self, handle the remark by mentioning the person.
Keep in mind
Point out customers by typing “@” and person, then decide the person from the listing. This not solely stands out within the feedback, but in addition triggers notification to the person in case they don’t seem to be watchers.
3, Attaching paperwork with out hyperlinks within the feedback
Simply dumping them right into a ticket and saying “file connected” is just not sufficient. It takes no further vitality to do it proper, so do it. Think about you might be given a job with 48 feedback and 14 attachments, and all of the customers are saying “file connected” – go determine.
Keep in mind
Begin the feedback first, then drag the attachment throughout – JIRA will add the hyperlink to your remark mechanically – that is it! You simply saved hours of wasted time and confusion. If the hyperlink does not come up mechanically, simply click on on the icon and choose it from the drop down.
4, Mentioning tickets with out [brackets]
All newcomers do it, however in case you have been utilizing JIRA for a short time it is time to cease it. Once more, not a lot effort is required and the advantages are priceless. In case you simply dump the ticket ID into the remark more often than not you get;
"Unable to render content material as a result of system error: String index out of vary: -1 "
Not solely this error cover what you needed to say, it’s also annoying to take away in case your permissions do not assist you to edit feedback.
Keep in mind
Any point out of a JIRA ticket must be in [brackets], for example MKEWS-42 => [MKEWS-42]. There are a number of advantages to this:
- It will not generate an error.
- You may click on on it instantly.
- You may see the ticket standing with out leaving the web page.
5, Not assigning tickets and altering standing
This is quite common when persons are exchanging quite a lot of feedback and do not wish to re-assign the ticket each time. But when your organization is coping with greater than 10 duties throughout all initiatives, which it hopefully does since you might be utilizing JIRA to handle it, it’s not possible to maintain observe of the subsequent motion. The identical goes for updating the standing. Are you simply utilizing “Open” and “Closed” statuses? Time to replace your flows to one thing helpful.
Keep in mind
The foundations are easy, if the ticket is in your title, you’re the one to progress it. Additionally, the tickets usually are not going to transition themselves to “Closed”. Understanding the standing of every ticket is crucial. JIRA makes use of statuses so customers need not keep in mind them and even worse, hold observe of them in a spreadsheet (sure, that is you I am speaking about).
6, Ticket hijacking
Everyone knows how this goes.
The monitoring code works tremendous, however after I view it on my cell, the picture does not resize...
Ticket hijackers trigger the tickets to go on endlessly and confuse everyone. But it surely takes two to tango. As the subsequent motion taker, you should not simply proceed with the brand new request. The following assignee (or anybody else engaged on the duty) has the ability to cease it and create a sub-task as a substitute. Sure, that is it.
Keep in mind
Every ticket is a job and that job solely. In case you found one thing new, it’s a new job. In case you spot a hijacker, create a sub-task.
7, Tickets with out data
That is the obvious one and sadly the commonest one too. Having the entire details about the duty is completely essential. There are not any shortcuts to this. No, a telephone name is just not OK. All the data must be on the ticket for everybody to see at any given time.
Keep in mind
Create each ticket as in case your grandma was to start out at your organization 2 years from now and she or he was the one to motion it.
#Lethal #Sins #JIRA #fundamentals