Jira has a massive problem. And it’s not even Jira’s fault.
Does any of this sound familiar?
This is all because of Jira tickets; not how Atlassian has created the platform – but how we, as users, are writing them.
Jira tickets, when written badly, can destroy productivity, cause friction, and lead vocal members of your team to demand a switch to a different platform. To avoid this, it’s important to know how to write Jira tickets effectively from the get-go.
Here are five ways to write better Jira tickets.
Always be clear, concise, and avoid any chance of ambiguity. If you’re worried about the ticket sounding rude, don’t. Wasting time with a super-long, ambiguous ticket is rude – giving the person the exact information they need is far kinder.
Assign exact names to features and user interface elements, and stick to them. Give actions rather than a laundry list of problems.
Most importantly of all, write a good title.
Use verbs (doing or action words) to prompt the action. For instance, do not simply write the feature you want – ask for the feature to be implemented.
The clearer your ticket can be from the start, the more likely it will be done without back and forth.
Format your tickets clearly, with bold text, italics, and clickable text links. Using markdown for specific text types can greatly improve the speed of writing Jira tickets – but you can achieve the same result with keyboard shortcuts.
Learn Jira’s markdown features and keyboard shortcuts.
Messy tickets take longer to read and longer to action – so make sure you clarify at the start with clean formatting.
A picture is worth a thousand words. So show, don’t tell.
Adding screenshots to a ticket, or a gif if the issue is time-based, will clearly show the recipient what the problem is, without you needing to explain much.
Before you start, your Jira admin must enable specific user permissions so that you can add attachments and screenshots – You need the “create attachments” permission.
Once you have it, you can drag and drop images, gifs, and other files into your Jira tickets. You can also browse your files by navigating to More > Attach files within Jira, while writing your ticket.
Make it as simple as possible – because often, things get complex when you’re trying to figure out if you’ve done what was needed.
At its most basic, your acceptance criteria should be a checklist; done or pending, true or false. In more detail, this includes your Definition of Done: a clear and concise description of what qualifies a task as complete.
So, focus on the reason for the ticket, and the outcome. Give it a clear list of qualifiers for being done. Make the language precise, free of ambiguity. And if possible, simplify it to true/false statements – so there’s absolutely no question of what “done” is.
You could write your Jira tickets in Word or Google Docs, to get spell checking and grammar fixes on the fly – or you could use a browser extension plugin like Grammarly, to fix it in-situ. Much faster!
Speaking of plugins, the Atlassian Marketplace is full of powerful add-ons to make Jira tickets more effective: like the Bitbucket plugin.
The Bitbucket plugin adds to the already seamless Jira and Bitbucket experience, by allowing the two tools to talk to each other. Simply include a Jira ticket number in a commit or pull request, and the Bitbucket activity will be tracked alongside the ticket.
Or how about the Slack plugin, which gives you chat notifications for any relevant ticket activity.
Jira can be customised so deeply, from the template level to plugins – so use it! Make the most of your tools, and get the best results.
And if you need support making Jira work exactly as you need it, we’re here to support you – with the brightest talent in the industry.
ClearHub specialises in finding freelance Jira experts – vetted, skills-checked and ready to work. To get started, call +44 (0) 2381 157811 or send your message to info@clearhub.tech.
ClearHub 2024 © All rights reserved | Privacy Policy | Trust Center | Modern Slavery Statement | Cookie Overview
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_BHWFTMS5QE | 2 years | This cookie is installed by Google Analytics. |
_gat_UA-91023414-2 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
_hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user. |
_hjIncludedInPageviewSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's pageview limit. |
_hjIncludedInSessionSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's daily session limit. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
Cookie | Duration | Description |
---|---|---|
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
TawkConnectionTime | session | Tawk.to, a live chat functionality, sets this cookie. For improved service, this cookie helps remember users so that previous chats can be linked together. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
_hjSession_1670766 | 30 minutes | No description |
_hjSessionUser_1670766 | 1 year | No description |
_referrer | 1 year | No description available. |
_utmz_cf7 | 1 year | No description available. |
AnalyticsSyncHistory | 1 month | No description |
li_gc | 2 years | No description |
popForm | 1 day | No description |
twk_idm_key | session | No description |
Cookie | Duration | Description |
---|---|---|
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |