QA Users Tips
QA Users Tips
As you type, JIRA will offer a list of "auto-complete" suggestions based on the context of query
Note: auto-complete suggestions only include the first 15 matches, displayed alphabetically, so it may
need to enter more text if a match cannot be found
Viewing a project's issues
Accessing a project and Viewing a project's issues
The project summary page is displayed which reveals recent activity and allows an easy
track of issues status in project.
Viewing a project's issues
Accessing a project and Viewing a project's issues
Manage user profile
Edit user details
Click profile picture -> Profile
Manage user profile
Edit user details
Click to edit -> display name -> email address -> password
Note: if JIRA administrator has configured the user directory with external password management, the
Change Password link will not be available.
Click to Edit Preferences -> choose Email Type -> My Changes select to receive notifications
about any changes made -> Click Update
Manage user profile
Other preferences options
Page size- > number of issues displayed on each Issue Navigator page
Time zone - > used for date and time information across JIRA applications
Sharing - > share filters and dashboards team or keep them restricted by default
.
Manage user profile
Other preferences options
My JIRA home - > Choose homepage. Homepage is the destination for the "JIRA" link in the header and the
first page you see when you log in.
JIRA keyboard shortcuts
JIRA shortcuts
Usually we find them accidentally, so here is a list of keyboard shortcuts for JIRA:
Type “?” on a non text area to see more shortcuts
Extension gadgets
Other gadgets are available as plugins on the Atlassian Marketplace. To use these plugins, you need
install them first (using the instructions provided with each plugin) then enable them
Story
Is a software system requirement that is expressed in a few short sentences, ideally using non-technical
language.
In JIRA Agile, a story is represented as an issue, and individual tasks within the story are
represented as sub-tasks.
Issues types in JIRA
Task
In JIRA Agile, individual tasks are represented as sub-task issues, and stories are represented as (parent)
issues.
Epic
It captures a large body of work. It is essentially a large user story that can be broken down into a
number of smaller stories. It may take several sprints to complete an epic.
JIRA and Outlook
How To Reduce the amount of email received from JIRA Issues
Outlook Rules: First of all, rules can be made to create a separate folder for email received from JIRA
Rules -> Create Rule -> Subject contains “JIRA” -> Send them to folder “JIRA”
JIRA and Outlook
How To Reduce the amount of email received from JIRA Issues
Stop Watching: Emails are received when any modification was made to a issue that you are watching
Click on Issue -> Stop Watching Issue
JIRA and Outlook
How To Reduce the amount of email received from JIRA Issues
Note: Use Stop watching for issue that no longer present interest for you or your team. Stop watching
by default can be set from User Profile Preferences, but is not indicated for QA users
Stop Watching using a Gadget: A Watched Issues widget can be added on a dashboard to have easy
access to all your watched issue
Rich-Text Fields
Editing Rich-Text Fields
When creating, editing or commenting on a JIRA issue, some fields may display two small icons at the
bottom of the text area
The presence of these icons indicates that this field supports JIRA's Text Formatting Notation, which
allows using rich-text features such as:
Header - > place "hn. " at the start of the line (where n is a number from 1-6). 1 - biggest, 6 – smallest
Anchor - > [#anchor] [^attachment.ext] - creates an internal hyperlink to the specified anchor or
attachment
Appending the '#' sign followed by an anchor name will lead into a specific bookmarked point of the
desired page. Having the '^' followed by the name of an attachment will lead into a link to the
attachment of the current issue.
Text Formatting Notation
Text Formatting Notation examples
Bullets - > * bullet ** indented
- different
* bulleted
*# with
*# nested
*# numbered
* list
Text Searching tips and tricks
Performing Text Searches
It applies to basic searches, advanced searches (when used with the CONTAINS operator) and also
applies to quick search when performing a text search on the fields that this feature supports.
Wildcard searches
? - > searches for words with a single character replaced ( e.g. te?t to search for "text" or "test" )
* - > the star replaces one or more characters (e. g. win* or w*n to search for “win98” or “Windows”) win*
Fuzzy searches
Wildcard searches
? - > searches for words with a single character replaced ( e.g. te?t to search for "text" or "test" )
* - > the star replaces one or more characters (e. g. win* or w*n to search for “win98” or “Windows”) win*
Fuzzy searches
OR
equivalent to a union using sets. || can be used instead of word OR (e.g. to search for issues that contain
either “X Y" or just “Z“, type X Y " || Z )
AND
equivalent to an intersection using sets. && can be used in place of the word AND( e.g. to search for issues
that contain “A B" and “C D“ type “A B" && “C D“ )
Text Searching tips and tricks
Required term
+ requires that the term after the "+" symbol exists somewhere in a the field of a single document ( e.g. to
search for issues that must contain “A" and may contain “B“ type +A B )
NOT
equivalent to a difference using sets. ! can be used instead of NOT and it excludes issues that contain the
term after ! ( e.g. to search for issues that contain “A B" but not “C” type “A B” !”C” )
Note: NOT cannot be used with just one term or at the beginning of a query
Text Searching tips and tricks
Note: using NOT over multiple fields may have irrelevant results because the search query is executed
over each field in turn, and the result set for each field is combined to form the final result set. Hence, an
issue that matches the search query based on one field, but fails based on another field will be included in
the search result set.
Grouping
Parentheses are used to group clauses to form sub queries. This can be very useful if you want to control
the Boolean logic for a query (e.g. to search for “X” and either “Y” or “Z” included type X AND (Y OR Z)
Note: do not use the grouping character '(' at the start of a search query, as this will result in an error. ( e.g.
"(X OR Y) AND Z" will not work.
Text Searching tips and tricks
Proximity searches
“two words"~n - > searches words that are within a specific distance away (e. g. “X Y"~10 example to search
for “X” and “Y" within 10 words of each other in a document
Boosting a term
word^n - > searches words by relevance level (e. g. atlassian^2 jira where “atlassian” is more relevant
because it has a boost factor 4; negative boost factors can be used too e.g. “ .2” for -2)
Excluding a term
- - > minus searches for issues that misses a certain word (e. g. “X Y”-Z to search for issues that contain X
and Y words but excludes Z word)
Text Searching tips and tricks
Reserved words
To keep the search performance optimal, JIRA ignores “stop words” such as:
Note: Searching with these words can sometimes lead to unexpected results
Example: searching for “game will crash” and then make another search with “ game will not crash” will
return both of these issues, because words “will” and “not” are part of reserved words list
Note: reserved words may not apply to all JIRA databases, as these stop words can be indexed by a JIRA
administrator
Links
Useful links
Q&A