JIRA

JIRA AN OVERVIEW
JIRA is the project tracker for teams planning, building and launching great products
We can use JIRA to capture and organize issues, work through action items, and stay up-to-
date with team actiity!
The JIRA Feature Tour
Why JIRA?
"o easily capture and organize our issues, prioritize and take action on what#s important,
and stay up-to-date with the actiity going on around you!
$rocess is eerything - we can %ustomize JIRA#s workflow to match the way our team
works!
$lan the work and work the plan! We can &uickly determine the work need to complete
and get the job done!
A simple, intuitie interface allows us to access the information we need, collaborate with
teammates, and get the job done
We can receie updates ia email, chat, or R''
We can also monitor actiity streams, dashboards, wallboards etc!,
Highlights
Brilliantly Simle to !se( JIRA#s configurable web interface is fast and intuitie with
keyboard shortcuts for eery issue action!
Tra"# Anything an$ E%erything( JIRA tracks eerything ) issues, tasks, features, and
of course, bugs! We can also define our own issue types to track the information that
matters most to us!
&anage Entire Ali"ation 'i(e )y"le* from concept to launch!
+lan Agile ,e%eloment( *reen+opper is an add-on for JIRA that makes Agile
accessible! It assists 'crum teams in planning their sprints and ,anban teams in
managing the flow of work!
)on(igure -our O.n Wor#(lo.( Workflow is customizable!
'in# Issues to Sour"e )o$e( -rop a JIRA issue key into any commit message to
instantly link related code changes, build status, code reiews, and more!
)onne"t to Anything( Want to link an issue to a re&uirements doc in %onfluence.
Remote issue links gie complete traceability from critical business applications down to
each line of code!
A$%an"e$ Sear"h an$ Reorting( JIRA /uery 'anguage 0J/'1 powers eerything
from the JIRA user interface to built-in project reports! It is especially useful for finding
elusie issues, running ad hoc reports, building dashboards, wallboards, and more!
Bug an$ Issue Tra"#ing*
/ug "racking is fast and can access issues directly from the I-0!
$ersonal dashboard can be configured to display issues 1Assigned to me2! 3sing 4pen
'ocial gadgets this can be shared with other Atlassian tools also!
Integrate Atlassian /onfire, for session-based e5ploratory ) or manual ) testing of web
applications
"he JIRA Issue %ollector is used to capture feedback from people outside the product
team!
Include JIRA 6obile %onnect in the mobile applications to collect feedback and engage
mobile users!
$re-built $roject Reporting is aailable!
JIRA imports issues and projects from irtually any bug tracker including /ugzilla,
6antis, "rac, 7ogbugz, $iotal "racker and more!
+ro2e"t Tra"#ing*
!se JIRA to "ature any tye o( issue ) from bugs and features to stories and
re&uirements to tasks and action items! -efine your own issue types to track the
information that matters most to your team!
)ustomi3e Wor#(lo. To Fit -our Team( %reate custom workflows to match your
e5isting processes and adapt &uickly to changes as your processes eole!
Agile +ro2e"t +lanning( Add *reen+opper to simplify planning and reporting when
using 'crum or ,anban!
+o.er -our +ro2e"t Wi#i( 8ink JIRA projects to the %onfluence spaces where you can
collaborate on specifications and re&uirements!
+ro2e"t Reorts an$ ,ash4oar$s( %hoose from pre-built project reports to analyze
time tracking, user workload and issue metrics! Run ad hoc reports using JIRA 9uery
8anguage :J98; for adding lists and charts to team dashboards!
Stay )onne"te$( <iew actiity streams for any project, issue or user by adding feeds to
your R'' reader or dashboard!
JIRA A$$5ons( 05tend JIRA with countless project management plugins and
integrations as per needed!
)o$e Integration*
JIRA 6 Sour"e( JIRA can be pointed to any repository and automatically link issues
directly to source! eg! /itbucket, *it or 6ercurial, *it+ub, *it /ehind the 7irewall,
'ubersion, $erforce, %<'!
Buil$ Noti(i"ations an$ Release &anagement( 8ink /amboo to connect issues with
builds! /amboo lets you see the latest build status on your dashboard and inside the
issues themseles! 'etup one-click release management with /amboo to streamline the
deployment process!
En"ourage )o$e Re%ie.( Add )ru"i4le 0Atlassian1 code reiews to the JIRA workflow
to ensure a second set of eyes looks oer eery line of code before it#s released into
production!
Reorting 7 Analysis(
A""ess imortant issues( $re-built system filters gie &uick access to the issues that
matter the most! We can sae and organize the faorite!
8ee the team in syn"( 'ae any search to create a filter! 'hare filters so eeryone can
&uickly access team priorities, working off the same list to achiee common goals!
Stay "onne"te$( 'ubscribe to shared filters to get email notifications at regular time
interals or when blockers pop up!
JIRA /uery 'anguage 0J/'1( 9uickly define custom searches with J98 using the
handy auto-complete &uery builder!
/ui"#ly 9enerate +ro2e"t Reorts( Run pre-built project reports for tracking time
spent, user workload and issue metrics! =aigate pre-defined filters ) or saed searches
) to triage issues re&uiring your attention!
Buil$ an$ Share ,ash4oar$s( %reate personal and team dashboards using a ariety of
Atlassian and 4pen 'ocial gadgets! "urn the dashboards into an information radiator,
proiding isibility to the whole team, using JIRA Wallboards!
)ustom Wor#(lo.*
)ustomi3e Wor#(lo.s To Fit -our +ro2e"ts( JIRA proides a default workflow and set
of issue type ideal for bug tracking and software deelopment! We can customize as per
the process we follow!
Visuali3e the Wor#(lo.( 3se the <isual Workflow -esigner to &uickly model your
processes! "he simple diagramming tool makes it &uick and easy to edit e5isting
workflows or build new ones from scratch!
)ontrol the Wor#(lo.( "ailor your workflow to ensure the right people are taking the
right steps at the right time! 'etup automatic actions to perform common or custom
tasks, like updating fields, generating eents, and more!
+oular JIRA A$$5ons ( %ustomize the workflow more effectiely using these Atlassian
add-ons
Featured Add-ons: So many Atlassian Add-ons are available as per the need or you can use
your own add-on.
S"reenshot Tour*
S"reen shot :( A clean and simple interface displays issue details, custom fields and workflow
actions!
S"reen shot ;* Tra"# Ongoing +ro2e"ts
<iew the project summary to find key project stats, reports and recent actiity!
S"reen shot <* )on(igure )ustom A"ti%ity Streams
"ailor actiity streams to show the type of information releant to you and your team! Add
actiity streams to your JIRA dashboard :shown here;, your R'' reader or any 4pen 'ocial
container!
S"reen shot =* )reate an$ Share ,ash4oar$s
%reate personal or shared team dashboards using 4pen 'ocial gadgets!
S"reen >* Fee$ -our In(ormation Ra$iator
"urn any dashboard into an information radiator using the JIRA Wallboard plugin!
S"reen ?* Visuali3e an$ E$it Wor#(lo.s
-esign custom workflows to match your deelopment process using the isual editor!
S"reen @* !se 8ey4oar$ Short"uts
=aigate JIRA and perform common operations without eer touching your mouse!
S"reen A* Issue Na%igator
=aigate search results and take action on issues using keyboard shortcuts in the Issue
=aigator!
S"reen B* )ommon Oeration ,ialogs
3pdate issues &uickly using pop-up dialogs accessible from issue details, search results and
the *reen+opper planning board!
S"reen :C* JIRA /uery 'anguage 0J/'1
3se the simple entry form with auto-complete to build J98 searches, find elusie issues and
drie powerful reporting capabilities!
JIRA 'i%e ,emo 'in#*
http(>>www!atlassian!com>software>jira>demo
JIRA !SER 9!I,E
JIRA )on"ets
What is a +ro2e"t?
A JIRA project is a collection of issues, and is defined according to the organization?s
re&uirements!
0g! A software deelopment project, a marketing campaign, a helpdesk system, a leae re&uest
, management system, a website enhancement re&uest system
0ery issue belongs to a project!
What is a "omonent?
A project component is a logical grouping of issues within a project! 0ach project may consist of
arious components :or none;, depending on the organization?s needs!
7or e5ample, a software deelopment project could consist of components called
#-ocumentation#, #/ackend#, #0mail 'ubsystem#, and @*3I?! A website enhancement re&uest
system might consist of components called #$roducts#, #%ontact 3s#, etc!
An issue can belong to zero, one or multiple components within a project
What is a %ersion?
7or some types of projects, particularly software deelopment, it is useful to be able to associate
an issue with a particular project version :e!g! A!B beta, A!B, A!C, C!B;!
T.o Tyes*
:D A((e"ts Version0s1 D this is the ersion:s; in which the issue is manifesting
;D FiE Version0s1 D this is the ersion:s; in which the issue was :or will be; fi5ed!
<ersions can be in one of three states( Release$F !nrelease$ or Ar"hi%e$D <ersions
What is Wor#(lo.?
Workflow is the moement :or transition; of an issue through arious Statuses during its
lifecycle!

What is an Issue?
An issue could represent a software bug, a project task, a helpdesk ticket, a leae re&uest form,
etc!
A JIRA issue tyi"ally loo#s li#e this*
"he numbered fields shown in the aboe screenshot are(
:D +ro2e"t D the #parent# project to which the issue belongs!
;D 8ey D a uni&ue identifier for this issue! :"he characters to the left of the hyphen
represent the project to which this issue belongs!
<D Summary D a brief one-line summary of the issue!
=D Tye D type of the issue
>D Status D the stage the issue is currently at in its lifecycle :#workflow#;!
?D +riority D the importance of the issue in relation to other issues
@D Resolution D a record of the issue#s resolution, if the issue has been resoled or
closed!
AD A((e"ts Version0s1 (if applicable) D project ersion:s; for which the issue is :or was;
manifesting!
BD FiE Version0s1 (if applicable) D project ersion:s; in which the issue was :or will be;
fi5ed!
:CD )omonent0s1 (if applicable) D project component:s; to which this issue relates!
::D 'a4els0s1 (if applicable) D labels to which this issue relates!
:;D En%ironment (if applicable) D the hardware or software enironment to which the issue
relates!
:<D ,es"rition D a detailed description of the issue!
:=D 'in#s D a list of links to related issues! :'trikethrough te5t, like this, indicates that an
issue has been resoled!;
:>D Assignee D the person to whom the issue is currently assigned!
:?D Reorter D the person who entered the issue into the system!
:@D Votes D the number shown in brackets indicates how many otes this issue has!
:AD Wat"hers D the no! shown in brackets indicates how many people who are watching
this issue!
:BD ,ue (if applicable) D the date by which this issue is scheduled to be completed!
;CD )reate$ D the time and date on which this issue was entered into JIRA!
;:D !$ate$ D the time and date on which this issue was last edited!
;;D Resol%e$ D the time and date on which this issue was resoled!
;<D Estimate D the Original Estimate of the total amount of time re&uired to resole the
issue, as estimated when the issue was created!
;=D Remaining D the Remaining Estimate, i!e! the current estimate of the remaining
amount of time re&uired to resole the issue!
;>D 'ogge$ --- the sum of the Time Sent from each of the indiidual work logs for this
issue
Tyes o( Issue *
Bug* A problem which impairs or preents the functions of the product!
Imro%ement* An enhancement to an e5isting feature!
Ne. Feature* A new feature of the product!
Tas#* A task that needs to be done!
)ustom Issue* A custom issue type, as defined by your organization if re&uired!
Tyes o( +riority*
Blo"#er* +ighest priority! It indicates that this issue takes precedence oer all others!
)riti"al* Indicates that this issue is causing a problem and re&uires urgent attention!
&a2or* Indicates that this issue has a significant impact!
&inor* Indicates that this issue has a relatiely minor impact!
Tri%ial* 8owest priority!
Tyes o( Status*
Oen* "his issue is in the initial #4pen# state, ready for the assignee to start work on it!
In +rogress* "his issue is being actiely worked on at the moment by the assignee!
Resol%e$* A Resolution has been identified or implemented, and this issue is awaiting
erification by the reporter! 7rom here, issues are either #Reopened# or are #%losed#!
Reoene$* "his issue was once #Resoled# or #%losed#, but is now being re-e5amined! :eg!,
an issue with a Resolution of #%annot Reproduce# is Reopened when more information becomes
aailable and the issue becomes reproducible;! 7rom here, issues are marked In ro!ress"
Resolved or #losed.
)lose$* "his issue is complete!
Tyes o( Resolution*
FiEe$* A fi5 for this issue has been implemented!
WonGt FiE* "his issue will not be fi5ed, e!g! it may no longer be releant!
,uli"ate* "his issue is a duplicate of an e5isting issue! =ote( it is recommended you
create a link to the duplicated issue!
In"omlete* "here is not enough information to work on this issue!
)annot Rero$u"e* "his issue could not be reproduced at this time, or not enough
information was aailable to reproduce the issue! If more information becomes aailable,
please reopen the issue!
9etting Starte$
'ogging in to JIRA
0nter your 3sername and $assword and click the 8og In button!
If you hae not changed your JIRA home page, the dashboard will be displayed!
4therwise, your chosen JIRA home page will be displayed instead!
Remem4er my login on this "omuter* 'electing this check bo5 will preent us from being
automatically logged out of JIRA on a gien browser and computer! /ut the session will not be
presered!
)anGt a""ess your a""ount? ---E %lick and go to that page(
'elect the $assword option and 0nter your username
'elect the 3sername option and enter your email address as in your JIRA user profile!
%lick 'end! =ew password will be emailed to the email address specified in your user
profile!
Sign u (or an a""ount :If JIRA admin has enabled public signup, you can create your own
user account;
%lick the 'ign up link in #=ot a member. 'ign 3p for an account#!
0nter your details! %lick the 'ign up button to create your account
EEloring the JIRA Wor#sa"e
,ash4oar$* It is the first page we see :by default; after logging in to JIRA!
"he naigation bar :at the top of the screen; is the same on eery screen in JIRA! It
contains links which gie &uick access to many of JIRA#s most useful functions!
"he white area of the screen, below the top naigation bar, can be customized to display
#gadgets# showing many different types of information, depending on your areas of
interest!
!sing 8ey4oar$ Short"uts
,eyboard shortcuts proide a &uick and easy way of naigating though JIRA and performing
fundamental actions on issues without haing to take your fingers off the keyboard!
To oen the #ey4oar$ short"uts $ialog 4oE*
%hoose your usernameGs $ro$o.n, then choose 8ey4oar$ Short"uts!
We can also open this dialo! bo$ by pressin! %?% (%Shift + /%) on your keyboard. &ote" your
cursor must not be focused in a 'IRA te$t field for %(% to work.
Screenshot: Keyboard Shortcuts Dialog Box in Firefox on Windos
!!!!! /e aware that when you press #.#, the keyboard shortcuts dialog bo5 will not appear if your
cursor is already focused inside any JIRA te5t entry field! $ress #0sc# first to escape from a field!
Wor#ing .ith an Issue*
:D Atta"hing a File
Atta"hing a File to an Issue
"o attach files to an issue, you need the )reate Atta"hments project permission in that issue#s
project
To atta"h a (ile to a JIRA issue*
A! 4pen the JIRA issue to which you wish to attach a file!
C! 7rom the #6ore Actions# menu, select Atta"h File!
F! "he #Attach 7iles# dialog bo5 will appear
G! %lick the Bro.se button to search for your files!
H! :4ptional; 0nter a comment about the files:s; you are attaching!
I! %lick the Atta"h button! All selected files will be attached to the issue
Vie.ing an Image 9allery
/y default, JIRA displays image files :ie! *I7s, J$*s, $=*s; attached to an issue, including any
screenshots, as #thumbnails# on the issue!
If your #JIRA administrator# has disabled #"humbnails# in JIRA#s Attachment 'ettings, then JIRA
will not display thumbnails of image files on an issue and instead, they will be part of the list of
attached files!
Sorting Atta"hments 0As"en$ingH,es"en$ing1
4pen a JIRA issue with attachments!
%lick the down-arrow icon to the right of the Atta"hments section and select the
re&uired sort criteria or order options proided in the list!
Jour final sort criteria and order options will also apply to image thumbnails and all
subse&uent issues iewed!
A""essing II+5(ormat File )ontents
"o browse the contents of a zipped attachment and access its files(
A! 4pen a JIRA issue with an attached zipped file!
C! %lick the right-arrow icon to the left of the zipped file#s name!
F! "he contents of the zipped file are listed! 7rom this e5panded list, you can access the
zipped file#s indiidual files by clicking their linked names or you can download the whole
zipped file in its entirety by clicking the ,o.nloa$ Ii link!
EEorting All Atta"hments as a II+ File
"o download all the files attached to an issue :including any screenshots; as a single
KI$ file(
Oen the JIRA Issue Atta"hments ,o.nloa$ All
Remo%ing a File Atta"hment (rom an Issue 0project permissions ,elete O.nHAll
Atta"hments needed1

"o remoe a file attachment from a JIRA issue( 4pen the JIRA issue select &anage
Atta"hments
The G&anage Atta"hmentsG age .ill aear*
;D Atta"hing a S"reenshot "his feature is only aailable if(
Jour JIRA administrator has file attachments enabled
Jou are using a Windows or 6ac client!
"he computer you are using to access JIRA uses a Jaa ersion A!IL platform!
"o attach a screenshot(
4pen the JIRA G&ore A"tionsG select GAtta"h S"reenshotG(
Capturing Screenshots
ALT-PRINTSCREEN to capture your currently selected window
CTRL-ALT-PRINTSCREEN to capture the whole desktop
<D )loning an Issue
#%loning# :copying; an issue allows you to &uickly create a duplicate of an issue within the same
project! "he clone issue can also be linked to the original issue using a #clone# link!
A clone issue is a separate entity from the original issue! 4perations on the original issue hae
no effect on the clone issue and ice ersa! "he only connection is a link :if created; between
the original and the clone issue!
A clone issue retains the following information(
'ummary D with optional prefi5 that can be customized by your JIRA system
administrator!
-escription
Assignee
0nironment
$riority
Issue "ype
'ecurity
Reporter :=ote that if you do not hae the G&o$i(y ReorterG permission, the clone issue
will be created with you as the Reporter!;
%omponents
Affects <ersions
7i5 7or <ersions
Issue 8inks :optional;
Attachments :optional;
$roject :once the clone has been saed, you can moe it to another project;
To "lone an issueF
Oen the JIRA Issue G&ore A"tionsG sele"t G)loneG )li"# J)reateK ButtonD
Jou can edit the clone issue#s 'ummary if you wish!
If the issue contains links to other issue:s;, you can select whether or not to include the
links in the new clone issue!
If the issue contains sub-tasks, you can select whether or not to create the sub-tasks in
the new clone issue!
If the issue contains attachments, you can select whether or not to include the
attachments in the new clone issue!
)lone$ Issue 'in#ing Beha%ior* JIRA will automatically create a link between the original and
cloned issue using the pre-e5isting link type name #%loners#!
)lone$ Issue Summary Fiel$ +re(iE* 'ummary# field of a cloned issue is prefi5ed with the
string #%84=0?
Cloning and Sub-Tasks: Sub-Tasks can also be cloned in the same manner as other issue types.
"#$%A Ad&inistrator can custo&i'e these default beha(iors in )onfiguring $ssue )loning*
=D )ommenting on an Issue
Adding comments to an issue is a useful way to record additional detail about an issue!
Adding a comment Permissions needed: Browse Project, Add Comments!
To add a comment: "pen the #IRA Issue Click $Comment% button In Comment te&t bo& enter
the comments and select an option 'rom $(ie)able b*% Click Add button+
Screenshot: Example comment with visibility restrictions
Collapsing and e&panding a comment
To 'collapse' a comment, Acti,it* section Browse the comment click Collapse icon of the comment
To epand! a comment, Acti,it* section Browse the comment click E&pand icon of the comment
Editing a comment: Permissions needed : Edit ")n-All Comments!
To edit a comment. Acti,it* section Browse the comment click Edit icon of the comment "dit
the comment's tet and#or (ie)able b* list $lick the Sa,e button
/eleting a comment : Permissions needed: /elete ")n-All Comments!
To delete a comment: Acti,it* section Browse the comment click /elete icon of the comment
Linking to a comment
To add Link to a comment: Acti,it* section Browse the comment click Permlink icon of the
comment
>D )reating an Issue
?D )reating a Su45Tas#
@D E$iting an Issue
AD E$iting Ri"h5TeEt Fiel$s
BD Emailing an Issue
:CD 'a4elling an Issue
::D 'in#ing Issues
:;D 'ogging Wor# on an Issue
:<D &o$i(ying &ultile 0GBul#G1 I
:=D &o%ing an Issue
:>D S"he$uling an Issue
:?D Setting Se"urity on an Issue
:@D Vie.ing an IssueGs )hange History
:AD Vie.ing an IssueGs )ru"i4le Re%ie.s
:BD Vie.ing an IssueGs FishEye )hangesets
;CD Vie.ing the Bam4oo Buil$s relate$ to an Issue
;:D Wat"hing an$ Voting on an Issue
Sear"hing (or Issues
9enerating Reorts
Bro.sing a +ro2e"t
7rom the project browser screen, we can browse the following(
+ro2e"t*
'ummary D 'hows recent actiity in your project, unreleased ersions and a chart
showing issue actiity! Reports are also located here!
Issues D 'hows a summary of all issues in a project grouped by 'tatus! Also shows
summaries of all unresoled issues, grouped by Assignee, $riority, <ersion and
%omponent!
Road 6ap D 'hows unresoled issues for upcoming ersions of a project!
%hange 8og D 'hows resoled issues for preious ersions of a project!
$opular Issues D 'hows a project#s unresoled issues, ordered by popularity :otes;!
<ersions M D 'hows a summary of recent ersions for a gien project!
%omponents M D 'hows a summary of all components for a gien project!
/uilds M D 'hows recent /amboo builds for a gien project!
'ource MM D 'hows recent 7ish0ye changesets for a gien project!
Reiews MM D 'hows recent %rucible code for a gien project!
Version*
<ersion 'ummary D 'hows recent actiity in a gien ersion of a project, plus a list of
issues that are due soon!
<ersion Issues D 'hows issues belonging to a gien ersion of a project!
<ersion $opular Issues D 'hows unresoled issues for a gien ersion, ordered by
popularity :otes;!
<ersion /uilds M D 'hows recent /amboo builds for a gien ersion!
)omonent*
%omponent 'ummary D 'hows recent actiity in a gien component of a project, plus a
list of issues that are due soon!
%omponent Issues D 'hows issues belonging to a gien component of a project!
%omponent Road 6ap D 'hows unresoled issues for a gien component, for
upcoming ersions of the project!
%omponent %hange 8og D 'hows resoled issues for a gien component, for preious
ersions of the project!
%omponent $opular Issues D 'hows unresoled issues for a gien component, ordered
by popularity :otes;!
M )nly available if *amboo inte!rated with 'IRA ()
++ )nly available if ,ish-ye inte!rated with 'IRA ()
Bro.sing a +ro2e"tGs Summary* %lick the project to iew %lick Summary "ab!
Bro.sing a +ro2e"tGs Issues* %lick the project to iew %lick Issues "ab
Bro.sing a +ro2e"tGs Roa$ &a* %lick the project to iew %lick Roa$ &a "ab
Bro.sing a +ro2e"tGs )hange 'og* %lick the project to iew %lick )hange 'og "ab
Bro.sing a +ro2e"tGs +oular Issues* %lick the project to iew %lick +oular Issues "ab
Bro.sing a +ro2e"tGs Versions* %lick the project to iew %lick Versions "ab
To 4ro.se a %ersionGs summaryF %lick the name of the ersion in which you are
interested! %lick the GSummary @tab! "he summary for your ersion will display :see
screenshot below; displaying the recently updated issues related to the ersion, by
default!
To 4ro.se a %ersionGs issuesL %lick the name of the ersion in which you are
interested! %lick the GIssuesG tab on the left of the page! "he issues summary for your
ersion will display!
To 4ro.se a %ersionGs oular issuesL %lick the name of the ersion in which you are
interested! %lick the G+oular IssuesG tab! "he unresoled popular issues for your
ersion will display! "o see resoled popular issues :instead of unresoled popular
issues;, click Gresol%e$ issuesGD
To %ie. the Bam4oo 4uil$ in(ormation relate$ to a %ersionF %lick the Buil$s tab
Bro.sing a +ro2e"tGs )omonents* %lick the project to iew %lick )omonents "ab
To 4ro.se a "omonentGs summaryF %lick the name of the component in which you
are interested! %lick the GSummaryG tab! "he summary for your component will display!
To 4ro.se a "omonentGs issuesL %lick the name of the component in which you are
interested! %lick the GIssuesG tab on the left of the page! Issues summary for your
component will display!
To 4ro.se a "omonentGs Roa$ &aF %lick the name of the component in which you
are interested! %lick the GRoa$ &a @tab! "he road map for your component will display!
To 4ro.se a "omonentGs )hange 'ogF %lick the name of the component in which
you are interested! %lick the G)hange 'og @tab! "he change log for your component will
display!
To 4ro.se a "omonentGs oular issuesL %lick the name of the component in which
you are interested! %lick G+oular IssuesG tab! 3nresoled popular issues for your
component will display!
Bro.sing a +ro2e"tGs 'a4els* %lick the project to iew %lick 'a4els "ab
Bro.sing a +ro2e"tGs Bam4oo Buil$s 0If JIRA is integrated with /amboo1
Jou can set up an R'' feed to track this information by clicking on the R'' icon in the top
left section of the page! 0ach entry in the list will display information about the related build,
including(
the build name and name of the build plan
when the build was last run
summary information, such as related builds, duration of the build, tests passed
build labels :if any;
links to build artifacts :if any;
Bro.sing a +ro2e"tGs FishEye )hangesets
JIRA#s )hangeset report allows you to iew recent changeset actiity for a project :that is,
where a JIRA issue key belonging to the project was referenced in the commit message;, if you
are using a source-code repository together with Atlassian 7ish0ye!
)ustomi3ing the ,ash4oar$
"he JIRA ,ash4oar$s is the first screen you see when you log in to JIRA! It can be
configured to display many different types of information, depending on your areas of
interest!
If you are anywhere else in JIRA, you can access your JIRA -ashboards iew by
clicking ,ash4oar$s at the top of your screen!
"he information bo5es on the dashboard are called 9a$gets(
So many 9a$gets are a%aila4leD .his !ad!et will only be available if it has been installed by
your 'IRA administrator
)reating a ,ash4oar$
"o create your own dashboard(
At the top right of the -ashboard, click the #Tools# menu!
'elect either #)reate ,ash4oar$# to create a blank dashboard, or #)oy ,ash4oar$# to
create a copy of the dashboard you are currently iewing!
Jou can now customize your dashboard as follows(
%hoosing a -ashboard 8ayout, Adding or 6oing or Remoing a *adget
)hoosing a ,ash4oar$ 'ayout
"o choose a different layout for your dashboard page :e!g! three columns instead of two;(
At the top right of the -ashboard, click the #E$it 'ayout# link! A selection of layouts will
be displayed(
%lick your preferred layout!
A$$ing a 9a$get
At the top right of the -ashboard, click the #A$$ 9a$get# link! A selection of gadgets will
be displayed!
'elect a category on the left to restrict the list of gadgets on the right to that category!
%lick the #A$$ it no.# button beneath your chosen gadget!
%lick the #Finishe$# button to return to your -ashboard!
If the gadget you hae selected re&uires configuration, you will be presented with the gadgets
configuration page! %onfigure appropriately and click #Sa%e#!
&o%ing a 9a$get* %lick the gadget and drag it into its new position!
Remo%ing a 9a$get*
+old your mouse oer the top right corner of the gadget, until a down-arrow appears!
%lick the down-arrow to display the following menu! %lick #,elete#!
&anaging &ultile ,ash4oar$ +ages
At the top left of the dashboard, click the down-arrow on the G,ash4oar$sG tab and select
G&anage ,ash4oar$G from the drop-down menu! G&anage ,ash4oar$sG page will display! In
this page, we can(
%reate a new dashboard page!
Add a dashboard page as a faourite!
'hare a dashboard page that you hae created, with other users!
'earch for dashboard pages that has been created by you or shared with you by other
users!
%onfigure or edit an e5isting dashboard that we hae created!
%opy a dashboard page that has been created by you or shared with you by other users!
-elete a dashboard page that you hae created!
To re5or$er the $ash4oar$ ages*
6oe a dashboard up %lick the up arrow of the dashboard
6oe a dashboard down %lick the down arrow for the dashboard that you wish to
moe!
6oe a dashboard to the top of the list %lick the curly up arrow of the dashboard!
6oe a dashboard to the bottom of the list %lick the curly down arrow of the
dashboard!
"o create a new dashboard(
At the top left of the dashboard, click the down-arrow on the G,ash4oar$sG tab and
select G&anage ,ash4oar$G from the drop-down menu!
"he G&anage ,ash4oar$sG page will display! It lists all the currently configured
dashboard pages!
%lick the G)reate ne. $ash4oar$G link! "he #%reate new dashboard# page will display!
0nter the -etails and %lick A$$, the dashboard will get added!
"o add an e5isting dashboard page to your dashboard(
G&anage ,ash4oar$G from the drop-down menu!
"he G&anage ,ash4oar$sG page will display! It lists all the currently configured dashboard
pages!
All the added dashboards will display under @&yK tab! Jour faourite dashboards are shown
with a yellow star! -ashboards that are not currently your faourite are shown with a grey
star! %lick the grey star icon ne5t to the name of the desired dashboard page to add it as a
faourite!
"he dashboard page will be displayed on your main dashboard!
"o remoe a dashboard page from your dashboard(
pages!
8ocate the dashboard page to be remoed from your dashboard under the GFa%oritesG tab!
%lick the star icon ne5t to the name of the dashboard page! "he dashboard page will be
remoed from your main dashboard!
"o share an e5isting dashboard page to the dashboard, please follow these steps(
pages! 8ocate the dashboard page that you wish to display on your dashboard under the
G&yG tab and click the GE$itG link for the dashboard in the GOerationsG column!
"he GE$it ,ash4oar$G page will display! 'elect the group, project or project role that you
want to share the dashboard with, or share it with all users, if you wish!
%lick the GA$$G link to add the share! Jou can add further share permissions if you wish!
%lick the G!$ateG button to sae your changes!
"o search for an e5isting dashboard page, please follow the steps below(
G&anage ,ash4oar$G from the drop-down menu! "he G&anage ,ash4oar$sG page will
display!
%lick the GSear"hG tab! "he dashboard 'earch will display! 0nter your search criteria and
click GSear"hG to run the search! 'earch results will be displayed on the same page
"o update the details of one of your e5isting dashboard pages, please follow the steps below(
display!
8ocate the dashboard page that you wish to update and click the GE$itG link for the
dashboard in the GOerationsG column!
"he GE$it ,ash4oar$G page will display! 3pdate the details of the dashboard page as
desired!
%lick the G!$ateG button to sae your changes!
%opying an e5isting -ashboard $age
display!
8ocate the dashboard page that you wish to copy and click the J)oyK link for the dashboard
in the GOerationsG column!
"he G)reate Ne. ,ash4oar$G page will display! 3pdate the details of the dashboard page
as desired!
%lick the #Add# button to sae your changes!
"o delete a dashboard pages, please follow the steps below(
display!
8ocate the dashboard page that you wish to delete and click the J,eleteK link for the
dashboard in the GOerationsG column!
A confirmation message bo5 will appear! "his message will also inform you if :and how
many; other users hae selected this dashboard as a faourite!
If you wish to continue with the deletion, click the G,eleteG button! 4therwise, click the #5# in
the top right of the message bo5 to cancel this action!
&anaging Other !serGs Share$ ,ash4oar$s
A shared dashboard is a dashboard whose creator has shared that dashboard with other users!
When a shared dashboard is created by a user, that user(
Initially #owns# the shared dashboard!
/eing the owner, can edit and modify the shared dashboard!
If you hae the #JIRA Administrators# global permission, you can manage shared dashboards
that were created by other users!
"o access the #'hared -ashboards# feature(
0nsure that you are logged in as a user with the JIRA Administrators global permission!
4n the top naigation bar, click the #-ashboards# dropdown and select #'hared
-ashboards# from the list!
)hanging the 'oo# an$ Beha%ior o( a 9a$get
"o hide or change the color of a gadget#s frame(
*o to the dashboard by clicking the #-ashboard# link or #+ome# link at the top left of the
screen!
"he dashboard will appear! 6oe the mouse pointer oer the gadget you want to
change! If the gadget#s frame is hidden, the frame will appear now!
%lick the dropdown menu icon at top right of the gadget frame!
"he dropdown menu will appear! %lick the color you want for your gadget#s frame! "o
hide the gadget#s frame, select the white color bo5 with red line in it!
&inimi3ing an$ EEan$ing a 9a$get
"o minimize a gadget , 6oe your mouse pointer oer the gadget you want to change!
"he gadget menu icons will appear! %lick the dropdown menu icon at top right of the
gadget!
"he dropdown menu will appear! %lick #6inimize#!
"o e5pand a gadget that has been minimized, 6oe your mouse pointer oer the gadget
you want to change!
"he gadget menu icons will appear! %lick the dropdown menu icon at top right of the
gadget!
"he dropdown menu will appear! %lick #05pand#!
To oen the maEimi3e$ or "an%as %ie. o( a ga$get,
6oe your mouse pointer oer the gadget you want to change!
"he gadget menu icons will appear! %lick the ma5imize icon at top right of the gadget
frame!
"his icon will appear only if the gadget proides a ma5imized or canas iew!
"he gadget#s ma5imized iew will open!
To "lose the "an%as %ie. an$ return to your $ash4oar$,
%lick the #Restore# option at the top right of the screen, or the #Restore# icon at top right of
the gadget frame!
To e$it a ga$getGs settingsF
6oe your mouse pointer oer the gadget you want to change! "he gadget menu icons
will appear!
%lick the dropdown menu icon at top right of the gadget frame! "he dropdown menu will
appear!
%lick #0dit#! A panel will open, showing the settings offered by the selected gadget!
Adjust the settings as re&uired then click #'ae#!
A$$ing the A"ti%ity Stream 9a$get
"he Actiity 'tream gadget displays a summary of recent actiity in particular projects!
"o add the #Actiity 'tream# gadget to your -ashboard(
*o to your JIRA dashboard and click Add *adget!
"he *adget -irectory will appear! 8ocate the Actiity 'tream gadget and click the A$$ it
no. button!
"hen click the (inishe$ button at the bottom of the *adget -irectory!
"he Actiity 'tream gadget will appear on your dashboard as follows, ready for you to
configure(
+o &o(e the gadget to a different ,osition on the dashboard- si&,ly drag-and-dro,.
A$$ing the A$ministration 9a$get
"he Administration gadget displays &uick links to administratie functions coneniently on the
dashboard! "o add this *adget(
*o to your JIRA dashboard and click #Add *adget#!
"he #*adget -irectory# will appear! 8ocate the #Admin# gadget and click the #Add it =ow#
button! "hen click the #7inished# button at the bottom of the *adget -irectory!
A$$ing the Assigne$ To &e 9a$get
"he @Assigne$ To &eK gadget displays all open issues in all projects assigned to the current
user iewing the dashboard! "o add the GAssigne$ To &eG gadget to your -ashboard(
*o to your JIRA dashboard and click Add *adget! "he *adget -irectory will appear!
8ocate the Watched Issues gadget and click the KA$$ it no.K button!
"hen click the @Finishe$? button at the bottom of the *adget -irectory!
The '%ssi&ned To 'e' &ad&et will appear on your dashboard as below.
"nter the details and click Sa(e
A$$ing the A%erage Age 9a$get
"he #Aerage Age# gadget displays a bar chart showing the aerage age :in days; of unresoled
issues at gien points in time! "o add the #Aerage Age# gadget to your dashboard(
*o to your JIRA dashboard and click #Add *adget#! "he #*adget -irectory# will appear!
8ocate the #Aerage Age# gadget and click the #Add it =ow# button!
"hen click the #7inished# button at the bottom of the *adget -irectory!
"he Aerage Age gadget will appear on your dashboard as follows, ready for you to
configure(
0nter the details and click 'ae!
/0+1:+o add Ba&boo gadgets- #$%A should ha(e been integrated ith ba&boo.
A$$ing the Bam4oo )harts 9a$get
"he /amboo %harts gadget displays arious charts and plan statistics from a particular
/amboo serer! "o add the #/amboo %harts# gadget to your -ashboard(
*o to your JIRA dashboard and click #Add *adget#! "he #*adget -irectory# will
appear!
8ocate the #/amboo %harts# gadget and click the #Add it =ow# button!
"he #/amboo %harts# gadget will appear on your dashboard as follows, ready for you
to configure!
%lick the arrow in the top right corner of the gadget to open the configuration menu
and click #0dit#!
%onfigure the /amboo information to be displayed on your gadget and %lick the
#'ae# button!
A$$ing the Bam4oo +lan Summary )hart 9a$get
"he /amboo $lan 'ummary %hart gadget displays a graphical summary of a /amboo build
plan from a particular /amboo serer! "o add the #/amboo $lan 'ummary %hart# gadget to your
-ashboard(
8ocate the #/amboo $lan 'ummary %hart# gadget and click the #Add it =ow# button!
"he #/amboo $lan 'ummary %hart# gadget will appear on your dashboard, ready for you
to configure!
%lick the arrow in the top right corner of the gadget to open the configuration menu and
click #0dit#!
%onfigure the /amboo information to be displayed on your gadget N %lick the #'ae#
button!
A$$ing the Bam4oo +lans 9a$get
"he /amboo $lans gadget displays a list of all plans on a particular /amboo serer and each
plan#s current status! "o add this *adget(
*o to your JIRA dashboard and click #Add *adget#!"he #*adget -irectory# will appear!
8ocate the #/amboo $lans# gadget and click the #Add it =ow# button!
"he #/amboo $lans# gadget will appear on your dashboard, ready for you to configure!
click #0dit#!
%onfigure the /amboo information to be displayed on your gadget N %lick the #'ae#
button!
A$$ing the Bug3illa I, Sear"h 9a$get
"he /ugzilla Issue I- 'earch gadget allows you to search all JIRA issues for references to
/ugzilla issue I-s! "o add this(
8ocate the #/ugzilla Issue I- 'earch# gadget and click the #Add it =ow# button!
"he #/ugzilla Issue I- 'earch# gadget will appear on your dashboard!
4ptionally enter the 3R8 of the /ugzilla serer you wish to search!
%lick the #'ae# button!
A$$ing the )alen$ar 9a$get
"he JIRA Issues %alendar gadget shows issues and ersions in a calendar format based on
their due date!
8ocate the #JIRA Issues %alendar# gadget and click the #Add it =ow# button!
"he JIRA Issues %alendar gadget will appear on your dashboard!
0nter the details N %lick the #'ae# button!
A$$ing the )lo%er )o%erage 9a$get
"he %loer %oerage gadget displays the %loer coerage of plans from a particular /amboo
serer!
*o to your JIRA dashboard and click #Add *adget?! "he #*adget -irectory# will appear!
8ocate the #%loer %oerage# gadget and click the #Add it =ow# button!
"he #%loer %oerage# gadget will appear on your dashboard as follows, ready for you to
configure!
click #0dit#!
%onfigure the information to be displayed on your gadget N %lick the #'ae# button!
A$$ing the )reate$ %sD Resol%e$ 9a$get
"he #%reated s! Resoled# gadget displays a difference chart showing the number of issues
created s! number of issues resoled oer a gien period of time! A report showing this
information is also aailable! "o add the #%reated s! Resoled Issues# gadget to your
-ashboard(
8ocate the #%reated s! Resoled# gadget and click the #Add it =ow# button!
"he #%reated s! Resoled# gadget will appear on your dashboard!
0nter the details N sae
A$$ing the )ru"i4le )harts 9a$get
"he %rucible %harts gadget displays arious charts showing statistical summaries of your code
reiews!
8ocate the #%rucible %harts# gadget and click the #Add it =ow# button!
"he #%rucible %harts# gadget will appear on your dashboard!
0nter the details and sae
A$$ing the Fa%ourite Filters 9a$get
"he 7aourite 7ilters gadget displays a list of all the issue filters that hae currently been added
by you as a #faourite# filter! "o add the #7aourite 7ilters# gadget to your -ashboard
8ocate the #7aourite 7ilters# gadget and click the #Add it =ow# button!
"he 7aourite 7ilters gadget will appear on your dashboard!
0nter the details and 'ae!
A$$ing the Filter Results 9a$get
"he 7ilter Results gadget displays the results of a specified issue filter on the dashboard!
8ocate the Watched Issues gadget and click the Add it =ow button!
"hen click the @Finishe$K button at the bottom of the *adget -irectory!
"he 7ilter Results gadget will appear on your dashboard!
A$$ing the FishEye )harts 9a$get
"he 7ish0ye %harts gadget displays two charts showing statistics about your source code
repository( 8ines of code, %ommit actiity! "o add the #7ish0ye %harts# gadget to your
-ashboard(
8ocate the #7ish0ye %harts# gadget and click the #Add it =ow# button!
"he #7ish0ye %harts# gadget will appear on your dashboard!
A$$ing the FishEye Re"ent )hangesets 9a$get
"he 7ish0ye Recent %hangesets gadget displays a number of recent changesets from a
7ish0ye repository! "o add the #7ish0ye Recent %hangesets# gadget to your -ashboard
8ocate the #7ish0ye Recent %hangesets# gadget and click the #Add it =ow# button!
"he #7ish0ye Recent %hangesets# gadget will appear on your dashboard!
A$$ing the In +rogress 9a$get
"he Issues in $rogress gadget displays all issues that are currently in progress and assigned to
you!
8ocate the #Issues in $rogress# gadget and click the #Add it =ow# button!
"he Issues in $rogress gadget will appear on your dashboard!
A$$ing the Intro$u"tion 9a$get
"he Introduction gadget displays a configurable introduction message on the dashboard!
8ocate the #Introduction# gadget and click the #Add it =ow# button!
"he Introduction gadget will appear on your dashboard!'
A$$ing the Issue Statisti"s 9a$get
"he Issue 'tatistics gadget displays the collection of issues returned from a specified project or
saed filter, grouped by a specified field!
8ocate the #Issue 'tatistics# gadget and click the #Add it =ow# button!
"he Issue 'tatistics gadget will appear on your dashboard!
A$$ing the JIRA Ne.s 9a$get
"he JIRA( =ews gadget displays recent Atlassian news about JIRA!
8ocate the #JIRA( =ews# gadget and click the #Add it =ow# button!
A$$ing the +ie )hart 9a$get
"he #$ie %hart# gadget displays issues returned from a specified project or issue filter, grouped
by a specified field!
8ocate the #$ie %hart# gadget and click the #Add it =ow# button!
"he $ie %hart gadget will appear on your dashboard!
A$$ing the +ro2e"ts 9a$get
"he $rojects gadget proides information and arious filters related to specified project:s; within
JIRA!
8ocate the #$rojects# gadget and click the #Add it =ow# button!
"he $rojects gadget will appear on your dashboard !
A$$ing the /ui"# 'in#s 9a$get
"he 9uick 8inks gadget displays a number of useful links to fre&uently-used searches and
operations!
8ocate the #9uick 8inks# gadget and click the #Add it =ow# button!
A$$ing the Re"ently )reate$ Issues 9a$get
"he #Recently %reated Issues# gadget displays a bar chart showing the rate, at which issues are
being created, as well as how many of those created issues are resoled!
8ocate the #Recently %reated Issues# gadget and click the #Add it =ow# button!
"he Recently %reated Issues gadget will appear on your dashboard!

A$$ing the Resolution Time 9a$get
"he #Resolution "ime# gadget displays a bar chart showing the aerage time taken to resole
issues! "his is useful to show you the trends in resolution time!
8ocate the #Resolution "ime# gadget and click the #Add it =ow# button!
"he Resolution "ime gadget will appear on your dashboard!
A$$ing the Roa$ &a 9a$get
"he Road 6ap gadget shows ersions which are due for release within a specified period of
time, and a summary of progress made towards completing the issues in those ersions!
8ocate the #Road 6ap# gadget and click the #Add it =ow# button!
"he Road 6ap gadget will appear on your dashboard
A$$ing the TeEt 9a$get
"he "e5t gadget displays your specified +"68 te5t on the dashboard!
8ocate the #"e5t# gadget and click the #Add it =ow# button!
"he "e5t gadget will appear on your dashboard!
A$$ing the Time Sin"e Issues 9a$get
"he #"ime 'ince# gadget displays a bar chart showing the number of issues for which your
chosen date field :e!g! #%reated#, #3pdated#, #-ue#, #Resoled#, or a custom field; was set on a
gien date!
8ocate the #"ime 'ince# gadget and click the #Add it =ow# button!
"he "ime 'ince gadget will appear on your dashboard!
A$$ing the T.o5,imensional Filter Statisti"s 9a$get
"he "wo -imensional 7ilter 'tatistics gadget displays statistical data based on a specified issue
filter, in a configurable table format!
8ocate the #"wo -imensional 7ilter 'tatistics# gadget and click the #Add it =ow# button!
"he "wo -imensional 7ilter 'tatistics gadget will appear on your dashboard!
A$$ing the Vote$ Issues 9a$get
"he <oted Issues gadget shows issues for which you hae oted!
"hen click the Finishe$ button at the bottom of the *adget -irectory!
"he <oted Issues gadget will appear on your dashboard
A$$ing the Wat"he$ Issues 9a$get
"he Watched Issues gadget shows issues which you are watching!
"hen click the 7inished button at the bottom of the *adget -irectory!
"he Watched Issues gadget will appear on your dashboard!
A$$ing the Heat &a 9a$get
"he +eat 6ap gadget displays the relatie weighting of alues of a specified field in issues
returned from a specified project or saed filter!
8ocate the #+eat 6ap# gadget and click the #Add it =ow# button!
"he +eat 6ap gadget will appear on your dashboard!
0nter the details and click the #'ae# button!
A$$ing the 'a4els 9a$get
"he 8abels gadget displays a list of all the labels in a specified project!
8ocate the #8abels# gadget and click the #Add it =ow# button!
"he 8abels gadget will appear on your dashboard!
&anaging your !ser +ro(ile
Jour JIRA user profile is where you specify your JIRA settings
To %ie. your JIRA user ro(ile*
%hoose your user name at top right of the screen, then choose +ro(ile
-- 0dit Icon, %lick the !$ate button to sae your changes!
3sing the 'ummary tab( 'ummary "ab %ontains, -
,etails * 7ull =ame, 0mail, $assword, Aatar, Administer ,0mail address, %hange
$assword,%lear All "okens ,Remember by login, <iew $roject Roles
2references:
Acti(ity Strea&: %lick any item to jump to an issue or other actiity in which you hae
recently participated! "he Actiity 'tream is also aailable as a gadget!
Filters:
3sing the Roadmap tab( "he Roa$ma tab page shows your #$ersonal Road 6ap# report,
which proides &uick access to work assigned to you across all projects!
3sing the "ools menu ( %lick the #Tools# menu in the top right to open it! 7rom this menu you
can, click Vie. OAuth A""ess To#ens to iew and edit the 4Auth "okens! %hange your
-ashboard layout, and add gadgets!
A$$ing a !ser A%atar
A user aatar is used as the icon for your profile to illustrate your comments on an issue and
your $rofile! To "hoose your user a%atar* click aatar icon
Allo.ing OAuth A""ess
4Auth access tokens allow you to(
3se a JIRA gadget on an e5ternal, 4Auth-compliant web application or website :also
known as a
#consumer#; A/D
*rant this gadget access to JIRA data which is restricted or priy to your JIRA user
account!
MM/efore this can happen, JIRA administrator must establish an 4Auth relationship with this
e5ternal web application or site by approing it as an 4Auth consumer
)hanging your +ass.or$
"o change your JIRA password( %hoose your user name at top right of the screen, then
choose +ro(ile!
In the ,etails section, click the #)hange +ass.or$# link
)hoosing a 'anguage 0user name +ro(ile+re(eren"esE$it I"on'anguage $ro
$o.n1
)hoosing a Time 3one 0user name +ro(ile+re(eren"esE$it I"onTimeIone $ro
$o.n1
!sing Ho%er +ro(ile
Ho%er +ro(ile is a conenient popup balloon that proides &uick access to key information
about other JIRA users throughout the JIRA interface and issues they hae been working on!
A""essing Ho%er +ro(ile 0moe or hoer your mouse oer a user#s username or (ull name on
issue F Issue Na%igatorF ro2e"t 4ro.ser1
)hanging your JIRA Home +age
Jou can configure the following JIRA pages as your JIRA home page( -ashboard, Issue
=aigator, Rapid /oard :aailable if you hae the *reen+opper plugin installed in JIRA;
To "on(igure your JIRA home age* 0!ser Name&- JIRA Home,ash Boar$H Issue
Na%igator1
JIRA A,&INISTRATORKS 9!I,E
9etting Hel
Where to Start
https(>>answers!atlassian!com>tags>jira> the Atlassian Answers site :JIRA 7orum;, where
Atlassian staff and JIRA users can answer your &uestions!
Raising a Suort ReMuest
8og in as a user with the JIRA 'ystem Administrators global permission!
%hoose Administration at the top right of your screen! "hen choose 'ystem E Atlassian
'upport
"ools from the menu bar at the top of the page!
%lick the 'upport Re&uest tab! "he 'upport Re&uestform will be displayed!
0nter the -etails and 'ubmit!
To raise a suort reMuest %ia the internet
$lease isit the Atlassian 'upport 'ystem :https(>>support!atlassian!com>; and create a support
re&uest! $lease proide as much information as possible, including any error messages that are
appearing on the console or in the logs! $lease also mention the operating system, database
and ersion of JIRA you are using!
To "reate a Suort Ii*
8og in as a user with the JIRA 'ystem Administrators global permission!
%hoose Administration at the top right of your screen! "hen choose 'ystem E Atlassian
'upport
"ools from the menu bar at the top of the page!
,eyboard shortcut( g L g L start typing support!
%lick the 'upport Kip tab! "he 'upport Kip page will be displayed!
8eaing all the bo5es tickedO click the %reate button at the bottom of the screen!
)on(iguring the 'ayout an$ ,esign
)ustomi3ing the 'oo# an$ Feel
8og in as a user with the JIRA Administrators global permission!
%hoose Administration at the top right of your screen! "hen choose 'ystem E 3ser
Interface E 8ook and 7eel!
"he 8ook and 7eel configuration page will be displayed!
%lick 0dit %onfiguration button and do the changes as needed!
"o sae your configuration changes, click the #3pdate# button!
"o leae edit mode and return to the #8ook and 7eel %onfiguration# page, click the
#%ancel# button!
"o reset JIRA back to its default look and feel, click the #Reset -efaults# button!
)hoosing a ,e(ault 'anguage
When JIRA is first installed, the default language may be chosen by clicking on a flag!
%hanging the default language
8og in as a user with the #JIRA Administrators# global permission!
%hoose Administration at the top right of your screen! "hen choose 'ystem E *eneral
%onfiguration to open the #Administration# page!
%lick the #0dit %onfiguration# button at the end of the page, then select the appropriate
language in the dropdown bo5 ne5t to #-efault language#!
Translating JIRA
"his page contains information about translating JIRA into languages other than 0nglish! "he
Atlassian "ranslations site :http(>>translations!atlassian!com>; proides a collaboratie
enironment for customers to translate JIRA!
What translations of JIRA are currently aailable. %urrently, JIRA ships with a number of
translations in the most commonly-re&uested languages! Jou can easily update these ia the
3niersal $lugin 6anager!
What about translations of the documentation. %urrently, not aailable!
)on(iguring the ,e(ault Issue Na%igator
"he Issue =aigator is used within JIRA to find and filter issues, and to display the search
results in arious formats :#iews#;! It is possible to select which issue fields will be displayed as
columns in the Issue =aigator!
JIRA administrators can configure which columns appear in the Issue =aigator by default, for
all users that do not hae their personal naigator columns configured!
%onfiguring the -efault Issue =aigator %olumns
Interface E =aigator %olumns to display the #Issue =aigator -efault %olumns# page!
"o moe a column left or right, click on the left-arrow or right-arrow icon that appears
under the column#s heading!
"o remoe a column from the list, click the bin icon which appears under the column#s
heading!
"o add a column to the list, select the issue field name from the drop-down bo5 titled
#Add =ew %olumn# and click the #Add# button! "he column will appear as the right-most
column in the list!
"o hide the #Actions# column, click the #+ide %olumn# link!
3sers can restore the global defaults by clicking the #Restore -efaults# link
)on(iguring the ,e(ault ,ash4oar$
"he default dashboard is the screen that all JIRA users see the first time they login! Any users
who hae not added any dashboard pages as faourites also see the default dashboard!
JIRA allows Administrators to configure the default dashboard! "he gadgets on the default
dashboard can be re-ordered, switched between the left and right columns, additional gadgets
can be added, and some gadgets can be configured! "he layout of the dashboard :e!g! number
of columns; can also be configured! "he layout of the dashboard :e!g! number of columns; can
also be configured!
Adding and %onfiguring *adgets on the -efault -ashboard
Interface E 'ystem -ashboard to open the #%onfigure 'ystem -ashboard# page!
'hortcut( #g# L #g# L #system dashboard#!
"o moe the current gadgets to a different position on the dashboard, simply drag N
drop them!
"o re-configure the e5isting gadgets, please see %hanging the 8ook and /ehaiour of a
*adget!
"o choose a different layout for the default dashboard, please see %ustomizing the
-ashboard!
!sing ,ash4oar$ 9a$gets
JIRA proides the ability to display summary information about project>issue data on the
dashboard, through the use of #gadgets#! 0ach gadget can be configured to display project and
issue details releant to particular users! *adgets can be added to the dashboard D proiding a
central location for &uick access to this information!
$re-installed gadgets ( JIRA proides a set of standard gadgets out-of-the-bo5(
05tension gadgets ( 4ther gadgets are aailable as plugins on the Atlassian 6arketplace!
If needed, we can integrate those gadgets!
%reating new gadgets ( =ew gadgets can be created by writing an P68 descriptor file,
packaged as an Atlassian plugin!
A$$ing a 9a$get to the ,ire"tory
"he JIRA gadget directory displays all the gadgets that are aailable for JIRA users to add to
their dashboard! Jou need to hae administrator priileges to add a gadget to the directory! If
you hae permission to add gadgets to and remoe gadgets from the directory itself, you will
see the #Add *adget to -irectory# and #Remoe# buttons on the #Add *adget# screen,
Su4s"ri4ing to Another Ali"ationGs 9a$gets
*o to the dashboard by clicking the #-ashboard# link or the #+ome# link at the top left of
the screen!
"he dashboard appears! %lick #Add *adget#!
"he #Add *adget# screen appears, showing the list of gadgets in your directory! %lick
#*adget 'ubscriptions#! Jou will only see this button if you hae administrator
permissions for your dashboard, and if your application supports gadget subscriptions!
"he #*adget 'ubscriptions# screen appears, showing the applications to which your
application already subscribes! %lick #Add 'ubscription#!
"he #Add 'ubscription# screen appears! 0nter the base 3R8 of the application you want
to subscribe to!
%lick @7inished? for adding the subscription!
)on(iguring an Announ"ement Banner
Administrators can configure an announcement banner to display pertinent information on all
JIRA pages! "he banner can be used to relate important information to all users! 7urther, the
banner isibility leel can be configured to display to all users or just logged-in users!
%onfiguring an Announcement /anner
Interface E Announcement /anner :tab; to open the #0dit Announcement /anner# page!
0nter the re&uired te5t in the Announcement field!
'elect the re&uired <isibility 8eel for the banner!
%lick the 'et /anner button!
/anner <isibility 6ode( +u4li" D the banner is isible to eeryone, +ri%ate D the
banner is isible to logged-in users only!
Ena4ling 'ogout )on(irmation
Administrators can configure JIRA to prompt users with a confirmation before logging them out!
/y default, JIRA will not prompt users to confirm logging out! "o change this(
8ocate the #4ptions# section(
/y default, JIRA will not prompt users to confirm logging out by default! "o change this,
click the #0dit %onfiguration# button at the end of the page!
"he #8ogout %onfirmation# field will now be editable! "he =eer and Always settings are
self-e5planatory! When set to %ookie, your JIRA users will only be prompted if they hae
logged in using a cookie :i!e! by selecting the #Remember my login on this computer#
check bo5 before they click the #8og In# button;!
!ser an$ 9rou &anagement
&anaging !sers
"o iew a list of JIRA users(
%hoose Administration at the top right of your screen! "hen choose 3sers E 3sers to
open the #3ser /rowser# page!
"o restrict the list of users shown in the 3ser /rowser, use the 7ilter form at the top of
the 3ser /rowser!
"o iew details and login information about a user in the list, click their 3sername or
0mail Address
A$$ing users
%reating a user
4pen the 3ser /rowser and click the Add 3ser button to open the #Add =ew 3ser# dialog
bo5!
0nter the 3sername :note that this alue cannot be changed once the user is created;,
$assword, 7ull =ame and 0mail address!
4ptionally, select the 'end =otification 0mail check bo5 to send the user an email
containing( their login nameO and a link from which to set their password :this link is alid
for CG hours;!
%lick the %reate button!
Initing users
Jou can inite one or more users to JIRA ia email! =ote( JIRA#s '6"$ mail serer must be
configured to send notifications before you can inite users ia email!
4pen the 3ser /rowser :see <iewing 3sers aboe; and click the Inite 3sers button to
open the #Inite 3sers# dialog bo5!
0nter the email addresses of the users that you want to inite! 0nter each address on a
new line or separate addresses using commas! :=ote, can?t inite users by sending an
initation to a mailing list!;
%lick the 'end button! An initation to create a user account in JIRA will be sent to each
email address!
0ach initation can only be used to create a user under the email address that it was
sent to, and can only be used once!
0ach initation will e5pire seen days after the day it was sent!
Jour user license count will not be affected until users accept the initation and the
users are created!
3sers that are created ia the initation will be added to the #jira-users# group!
Assigning a user to a group
8ocate the user in the 3ser /rowser :see <iewing 3sers aboe; and click the *roups
link in the 4perations column!
"his will display two listsO the one on the left shows all aailable groups, and the one on
the right shows all groups to which the user currently belongs! 3se the Join and 8eae
buttons to add the user to or remoe them from your selected group!
Assigning a user to a project role
Assigning a user to a project role enables them to fulfill a particular function in a
particular project!
"o iew a user#s project role membership, locate the user in the 3ser /rowser and click
the $roject Roles link in the 4perations column!
"his will display a table showing all the projects and project roles that e5ist in JIRA, and
the user#s current project role membership for each project!
%lick the 0dit $roject Roles button! "he check bo5es will then be aailable for you to
select :to add the user to a project role; or clear :to remoe the user from a project role;!
%hanging a user#s name or email address
8ocate the user in the 3ser /rowser and click their 0dit link in the 4perations column!
In the resulting form, make the re&uired changes the user#s 7ull =ame and>or 0mail
address!
-o not clear the Actie check bo5 unless you want to deactiate this user!
%lick 3pdate to confirm the change!
%hanging a user#s password
8ocate the user in the 3ser /rowser and click their 3sername! "his displays the user#s
details!
%lick the 'et $assword link! "his displays the 'et $assword screen!
0nter and confirm the new password!
%lick the 3pdate button!
Adding a property to a user
8ocate the user in the 3ser /rowser N click their 3sername! "his displays the user#s
details in a bo5!
%lick the 0dit $roperties link towards the end of the page! "his displays the 0dit 3ser
$roperties screen
0nter the new ,ey and its <alue, and then click the Add button!
"o deactiate a user account(
8ocate the user in the 3ser /rowser and click their 0dit link in the 4perations column!
In the resulting form, clear the Actie check bo5!
%lick 3pdate to confirm the change!
"o re-enable the user again, repeat the steps aboe but instead, select the Actie check
bo5!
"o delete a user(
8ocate the user in the 3ser /rowser and click the -elete link in the 4perations column!
"he confirmation screen that follows will summarize the user details!
&anaging 9rous
A JIRA group is a conenient way to manage a collection of users! 3sers can belong to many
groups! *roups are used throughout JIRAO for e5ample, they can(
/e granted global permissions!
/e used in project permission schemes!
/e used in email notification schemes!
/e used in issue security leels!
/e gien access to issue filters!
/e gien access to dashboards!
/elong to project roles!
JIRAGs $e(ault grous
9rou ,es"rition
2ira5a$ministrators is a member of the #Administrators# project role!
has the #JIRA Administrators# and the #JIRA 'ystem
Administrators# global permissions!
2ira5$e%eloers is a member of the #-eelopers# project role!
has the #/rowse 3sers#, #%reate 'hared 7ilter# and #6anage
*roup 7ilter 'ubscriptions# global permissions!
2ira5users is a member of the #3sers# project role!
has the #JIRA 3sers# and #/ulk %hange# global permissions!
Vie.ing grous
%hoose Administration at the top right of your screen! "hen choose 3sers E *roups to
open the #*roups# page!
"o see which permission schemes, email notification schemes, issue security leels and
saed filters are using this group, click the group name!
Adding a group( "o create a group, enter the new group #=ame# in the #Add *roup# form in the
#*roup /rowser# and click the #Add *roup# button!
-eleting a group( "o delete a group, click the #-elete# link for that group in the #*roup /rowser#
0diting group membership( "o edit a group#s membership, click the #0dit 6embers# link in the
row for that group in the #*roup /rowser#! A form will open to add users to or remoe them from
the group!
"o automatically add newly-created users to a particular group, you can either(
*rant the group the #JIRA 3sers# global permission!
'pecify the group name in the #-efault *roup 6emberships# option when connecting to
an 8-A$ -irectory!
&anaging +ro2e"t Roles
$roject roles are a fle5ible way to associate users and>or groups with particular projects!
JIRAGs $e(ault ro2e"t roles
9rou ,es"rition
A$ministrators "ypically contains people who administer a gien project!
,e%eloers "ypically contains people who work on issues in a gien project
!sers "ypically contains people who log issues in a gien project!
<iewing project roles
%hoose Administration at the top right of your screen! "hen choose 3sers E Roles to
open the #$roject Role /rowser# page!
"he $roject Role /rowse contains a list of all the project roles in your JIRA system
"o see where a project role is used, click the #<iew 3sage# link! "his will display a list of
the project role#s associated permission schemes, email notification schemes, issue
security leels and workflow conditions!
Adding a project role( "o define a new project role, enter its =ame :uni&ue; and a -escription in
the #Add $roject Role# form in the $roject Role /rowser , and click the #Add $roject Role# button!
-eleting a project role( "o delete a project role, locate the project role in the $roject Role
/rowser and click the #-elete# link!
0diting a project role( "o edit the =ame and -escription of a project role, locate the project role
in the $roject Role /rowser and click the #0dit# link! "his takes you to a form where you can
modify the project role#s #=ame# and #-escription#!
'pecifying #default members# for a project role
4pen the $roject Role /rowser!
%lick the #6anage -efault 6embers# link!
%lick the #0dit# link in the Administrators column :ne5t to #=one selected#;!
In the #Assign -efault 3sers to $roject Role# screen, click the #3ser $icker# icon!
8ocate 'usie in the #3ser $icker# popup window, and then click the #'elect# button!
In the #Assign -efault 3sers to $roject Role# screen, click the #Add# button!
&igrating !ser 9rous to +ro2e"t Roles
$roject roles are a fle5ible way of associating particular users and groups with a particular
project!
Why migrate to $roject Roles.
0ase of management D /y implementing project roles, you may be able to reduce the
number of groups, permission schemes and notification schemes in your JIRA system!
"his can make your system easier to manage!
-elegated administration D A project administrator can assign users and groups to
project roles for their project! If their project#s permission scheme and notification
scheme are using project roles, the project administrator can control who may access
their project and who receies email notifications!
3pdating $ermission 'chemes and =otification 'chemes to use $roject Roles instead of
*roups
*efore you be!in/ *ack up your e$istin! 'IRA data!
%hoose Administration at the top right of your screen! "hen choose 'ystem E Adanced
E 'cheme "ools to open the #'cheme "ools# page!
%lick the #*roup to $roject Role 6apping "ool# link!
"his will display the #6ap *roups to $roject Roles( 'elect 'chemes# page(
=ote that schemes that are not associated with any projects need not usually be
included in this processO but if you wish to select from all schemes in your system
:including unused schemes;, click #All#!
3nder #'tep A( 'elect a scheme type#, select whether you want to update
permission schemes or notification schemes! :Jou can only do one type of
scheme at a time, but you can easily come back and do the other type later;!
3nder #'tep C( 'elect the schemes to work with#, select the schemes you want to
update to use project roles instead of groups! Jou can use the #%trl# key to select
multiple schemes!
%lick the #6ap *roups to Roles# button!
"his will display the #6ap *roups to $roject Roles( 'elect 6appings# page( 7or each
group, select the project role that will replace itO or, for any groups that you do not want
to migrate, choose the #-o not map group# option! "hen click the #$reiew 6appings#
button!
Jou will now see the #6ap *roups to $roject Roles( $reiew "ransformation for
'chemes# page(
If you are satisfied that the information shown on this page is correct, click the #'ae#
button to(
%reate a backup of the scheme:s; that you selected! "his backup scheme will not
be associated with any projects!
update the scheme:s; that you selected
Add the users :in the right column of the table; to the project role :in the left
column of the table; for each project that uses the scheme! "his ensures that all
users will continue to hae the same permissions and notifications!
Jou will now see confirmation of the aboe changes on the #6ap *roups to $roject
Roles( Results of "ransformation for 'chemes# page(
After updating your permission schemes and notification schemes to use project roles
instead of groups, you may find that many of your schemes are now ery similar!
6inimizing the number of $ermission 'chemes and =otification 'chemes
%hoose Administration at the top right of your screen! "hen choose 'ystem E Adanced
E 'cheme "ools to open the #'cheme "ools# page!
%lick the #'cheme %omparison "ool# link!
"his will display the #'cheme %omparison( 'elect 'cheme# page(
=ote that schemes which are not associated with any projects need not usually
be included in this processO but if you wish to select from all schemes in your
system :including unused schemes;, click #All#!
3nder #'tep A( 'elect a scheme type#, select whether you want to compare
permission schemes or notification schemes! :Jou can only do one type of
scheme at a time, but you can easily come back and do the other type later!;
3nder 'tep C( 'elect the schemes to work with, select the schemes you want to
compare! 'elect at least C :and no more than H; schemes, using the #%trl# key to
select multiple schemes!
%lick the #%ompare 'chemes# button!
"his will display the #'cheme %omparison( <iew 'cheme -ifferences# page( If you
decide it is appropriate to edit a scheme to make it the same as another one, you can
edit the scheme by clicking the scheme name!
"hen repeat the steps aboe, and erify that you hae achieed a batch of C or more
identical permission schemes
%lick the #6erge -uplicate 'chemes "ool# link!
Jou will now see the #6erge 'chemes( %hoose 'chemes to 6erge# page(
If you decide it is appropriate to merge the displayed schemes(
%heck the bo5 ne5t to the scheme names!
"ype a name for the new scheme in the #=ew 'cheme =ame# bo5!
%lick the #$reiew %hanges# button!
Jou will now see the #6erge 'chemes( $reiew Results# page(
If you are satisfied that the information shown on this page is correct, click the #'ubmit
%hanges# button!
Jou will now see confirmation of the aboe changes on the #6erge 'chemes( Results#
page(
%lick the #/ulk -elete 'chemes "ool# link
Jou will now see the #/ulk -elete 'chemes( 'elect 'chemes# page(
you decide it is appropriate to delete the displayed schemes(
%heck the bo5 ne5t to the scheme names!
"ype a name for the new scheme in the 2=ew 'cheme =ame2 bo5!
%lick the #2$reiew# button! =ote that deleting these schemes will not affect any projects,
as this page only displays schemes that are not associated with projects!
Jou will now see the #/ulk -elete 'chemes( %onfirm 'chemes to -elete# page(
If you are satisfied that the information shown on this page is correct, click the #-elete
'chemes# button!
Jou will now see the #/ulk -elete 'chemes( Results# page, confirming that the unused
schemes hae been deleted!
Vie.ing !ser Sessions
JIRA proides a list of users who are currently accessing JIRA! "o iew a list of current JIRA
user sessions(
8og in as a user with the #JIRA 'ystem Administrators# global permission!
%hoose Administration at the top right of your screen! "hen choose 'ystem E 'ecurity E
3ser
'essions :tab; to open the #%urrent 3ser 'essions in JIRA# page!
"o administer a user, click a username to go to the user#s $rofile, then select #Administer
3ser# from the #"ools# menu
!ser a""ess logging
4ccasionally one wishes to get an oerall picture of which users are accessing which pages in
JIRA!
3R8 logging is disabled in JIRA by default! "o turn it on :JIRA G!5;(
%hoose Administration at the top right of your screen! "hen choose 'ystem E
"roubleshooting and 'upport E 8ogging N $rofiling to open the #8ogging# page, which
lists all defined logGj categories :as package names; and their current logging leels!
%lick the #0nable# link on #+""$ Access 8ogging# and #'4A$ Access 8ogging#!
Ali"ation Ser%er A""ess 'ogs
JIRA#s application serer :Apache "omcat; can also produce access logs! "hese are enabled
by default in JIRA and result in logs>accessQlog!RdateE!log files being generated in your JIRA
Installation -irectory!
)learing GRemem4er my loginG To#ens
"o ma5imize and maintain the security of your JIRA site, JIRA proides features for(
clearing #Remember my login# tokens associated with indiidual user accounts
%learing all #Remember my login# tokens stored by your JIRA site!
%learing #Remember my login# "okens from a 3ser $rofile
A JIRA user can clear all of their own #Remember my login# tokens from JIRA through their user
profile! "o do this(
<isit your 3ser $rofile!
In the -etails section, click the #%lear All "okens# link! "he Remember my login message
bo5 appears!
%lick the #%lear All "okens# button! All tokens associated with your user account will be
remoed from the JIRA serer!
%learing a 3ser#s #Remember my login# "okens from the Administration %onsole
%hoose Administration at the top right of your screen! "hen choose 3sers E 3sers to
open the #3ser /rowser# page!
%lick the 3sername or 0mail Address of the user whose #Remember my login# tokens
you wish to remoe! -etails about that user and their login information are displayed!
"o restrict the list of users shown in the 3ser /rowser, use the 7ilter form at the top of
the 3ser /rowser! 'pecifying :part of; the user#s email and>or group, then clicking the
#7ilter# button, will reduce the list to only those users who match those criteria!
%lick the #Remember 6y 8ogin# link to display that user#s Remember 6y 8ogin page!
%lick the #%lear All# button to remoe all #Remember my login# tokens associated with this
user account from the JIRA serer!
%learing all #Remember my login# "okens from the JIRA site
%hoose Administration at the top right of your screen! "hen choose 'ystem E 'ecurity E
Remember 6y 8ogin to open the #Remember 6y 8ogin for All 3sers# page!
%lick the #%lear All# button to remoe all #Remember my login# tokens from the JIRA
serer!
-isabling Remember 6y 8ogin on this %omputer
"he check bo5 for this option can be disabled by setting the jira!option!allowcookies
property to false in your jira-config!properties file! Jou will need to restart JIRA in order
for this change to take effect!
0dit the !>atlassian-jira>includes>loginform!jsp file!
Ena4ling +u4li" Signu an$ )A+T)HA
7or some organizations it is appropriate to enable signup, which allows isitors to immediately
create their own JIRA user accounts! If signup is not enabled, then only a JIRA administrator
can create new user accounts! If your JIRA serer is accessible from outside your organization?s
firewall, and you hae enabled signup, then you may want to also enable %A$"%+A
0nabling $ublic 'ignup
%lick #0dit %onfiguration# at the end of the page!
In the #6ode# drop-down, select #$ublic#!
%lick the #3pdate# button at the bottom of the screen!
8og out of JIRA, then click the #8og In# link at the top right of the screen and erify that
the #'ign 3p# link is displayed at the bottom of the login screen(
0nabling %A$"%+A
%lick #0dit %onfiguration# at the end of the page! 8ocate #%A$"%+A on signup# and select
#4n#!
%lick the #3pdate# button at the bottom of the screen!
8og out of JIRA, click the #8og In# link at the top right of the screen, then click the #'ign
3p# link and erify that a random se&uence of letters is displayed at the bottom of the
#'ign 3p# screen!
+ro2e"t &anagement
,e(ining a +ro2e"t
)reating a ro2e"t
"o add a new project in JIRA(
%hoose Administration at the top right of your screen! "hen choose $rojects E $rojects
to open the #$rojects# page!
%lick Add $roject to open the Add a new project dialog bo5!
4nce created, the $roject 'ummary administration page will be displayed as shown
below!
)on(iguring a ro2e"t
"o start to configure a project in JIRA(
%hoose Administration at the top right of your screen!
"hen choose $rojects from the menu bar and select the name of the project of interest!
4therwise, choose your project from the $rojects list or $roject %ategories!
"o edit the project#s details(
%lick 0dit $roject at the top of the $roject 'ummary page!
In the resulting 0dit $roject dialog bo5, edit the following fields( =ame, 3R8, $roject
Aatar and -escription!
%lick the link ne5t to the %ategory field :located under the project name; to assign the
project into a logical category>group! "his is useful for managing multiple related
projects!
If no categories e5ist, click the Add link on the following =o $roject %ategory page to add
a new category! =ew categories can also be created ia Administration E $rojects E
$roject %ategories!
Issue tyes
JIRA enables us to keep track of different types of things D bugs, tasks, helpdesk tickets, etc!
D by using different issue types! We can also configure each issue type to act differently, e!g! to
follow a different process flow or track different pieces of information!
Issue "ype 'cheme D the project#s issue type scheme determines which issue types apply to
this project!
Wor#(lo.s
A workflow defines the se&uence of steps :or statuses; that an issue will follow, e!g! 4pen, In
$rogress, and Resoled! Jou can configure how issues will transition between statuses, e!g!
who can transition them, under what conditions, and which screen will be displayed for each
transition!
Workflow 'cheme D the project#s workflow scheme determines which workflows :issue state
transitions; apply to issue types in this project!
S"reens
A screen is simply a collection of fields! Jou can choose which screen to display when an issue
is being created, iewed, edited, or transitioned through a particular step in a workflow!
'creen 'cheme D the project#s screen scheme determines which screens are displayed for
different issue operations :iew, edit, create;O
Issue "ype 'creen 'cheme D the project#s issue type screen scheme determines which
screens are displayed for different issue operations :iew, edit, create;, for different issue types!
Fiel$s
JIRA enables you to define field behaiour( each field can be re&uired>optional, rich te5t>plain
te5t, hidden>isible! We can define this behaiour by using a field configuration!
7ield %onfiguration 'cheme D the project#s field configuration scheme determines which field
configuration applies to issue types in this project!
Settings
%<' 6odules D configures %<' integration for this project!
Application 8inks D projects or other entities on other applications or sites to which this JIRA
project has been linked ia application links! =ew project>entity links can be created by clicking
the %onfigure Application 8inks# link! 'ee Adding $roject 8inks between Applications for details!
Roles
-ifferent people may play different roles in different projects D the same person may be a
leader of one project but an obserer of another project! JIRA enables you to allocate particular
people to specific roles in your project!
$roject 8ead D user fulfilling the role of project leader! 3sed as the #-efault Assignee# and
potentially elsewhere in JIRA :e!g! in permission schemes, notification schemes, issue security
schemes and workflows;!
-efault Assignee D the user to whom issues in this project are initially assigned when created!
%an be either the #$roject 8ead# :aboe;, or, if Allow unassigned issues is set to #4n# in JIRA#s
general configuration, #3nassigned#! "here are also default component assignees!
$roject Roles D members are users>groups who fulfill particular functions for this project!
$roject roles are used in permission schemes, notification schemes, issue security schemes
and workflows!
Versions
If you are using JIRA to manage the deelopment of a product, you may want to define different
ersions to help you track which issues relate to different releases of your product :e!g! A!B, A!A,
A!C, C!B beta, C!B;! JIRA can help you manage, release and archie your ersions! <ersions can
also hae a Release -ate, and will automatically be highlighted as 2oerdue2 if the ersion is
unreleased when this date passes!
<ersions D ersions defined in the project!
)omonents
Jou may want to define arious components to categorize and manage different issues! 7or a
software deelopment project, for e5ample, you might define components called 2-atabase2,
23sability2, 2-ocumentation2 :note that issues can belong to more than one component;! Jou
can choose a -efault Assignee for each component, which is useful if you hae different people
leading different sub-teams in your project!
%omponents( logical groups that this project#s issues can belong to!
+ermissions
JIRA allows you to control who can access your project, and e5actly what they can do :e!g!
2Work on Issues2, 2%omment on Issues2, 2Assign Issues2;, by using project permissions! Jou
can also control access to indiidual issues by using security leels! Jou can choose to grant
access to specific users, or groups, or roles!
$ermission 'cheme D the project#s permission scheme determines who has permission to iew
or change issues in this project!
Issue 'ecurity 'cheme D the project#s issue security scheme determines what isibility leels
issues in this project can hae!
Noti(i"ations
JIRA can notify the appropriate people when a particular eent occurs in your project :e!g!
2Issue %reated2, 2Issue Resoled2;! Jou can choose specific people, or groups, or roles to
receie email notifications when different eents occur!
=otification 'cheme D the project#s notification scheme determines who receies email
notifications of changes to issues in this project!
0mail D specifies the #7rom# address for emails sent from this project! 4nly aailable if an
'6"$ email serer has been configured in JIRA!
A ro2e"t a$ministrator in JIRA is someone who has the project-specific Administer $rojects
project permission, but not necessarily the JIRA Administrator global permission! Without the
JIRA Administrator global permission, howeer, project administrators can do the following(
0dit the project name
0dit the project description
0dit the project aatar image
0dit the project 3R8
0dit the project lead
0dit project role membership
-efine project components
-efine project ersions
<iew, but not select nor edit the project#s schemes :notification > permission scheme,
etc!;
&anaging +ro2e"t Role &em4ershi
A JIRA project role is a fle5ible way to associate users and>or groups with a particular project!
3nlike groups, which hae the same membership throughout JIRA, project roles hae specific
members for each project! 3sers may play different roles in different projects!
"o see which users and groups belong to each project role for a particular project(
8og in to JIRA as a project administrator!
%hoose Administration at the top right of your screen!
"hen choose $rojects from the menu bar and select the name of the project of interest!
4therwise, choose your project from the $rojects list or $roject %ategories!
"he #$roject 'ummary# page for your selected project is shown!
8ocate the Roles section at the right of the #$roject 'ummary# page and click the <iew
$roject Roles link to display the Roles page!
"he Roles page is displayed, from where you can manage the project role membership
as described below!
Assigning a user to a project role
4pen the Roles page and hoer oer the 3sers column for the project role in which you
are interested and click the yellow bo5 which appears!
"he users and groups will become editable! "ype the name of the user:s; you wish to
add to this project role!
"he /rowse 3sers global permission is re&uired to search for users in the 3sers column!
If you do not hae this permission, you will need to specify the e5act name of the
user:s;, followed by the #0nter# key after each user specified!
%lick the !$ate button!
Remoing a user from a project role
4pen the Roles page!
+oer oer the !sers column for the project role in which you are interested and click
the yellow bo5 which appears! "he users and groups will become editable
%lick the E ne5t to the name of the user:s; you wish to remoe from this project role!
%lick the !$ate button.
Assigning a group to a project role
4pen the Roles screen!
+oer oer the 9rous column for the project role in which you are interested and click
the yellow bo5 which appears! "he users and groups will become editable!
"ype the name of the group:s; you wish to add to this project role!
"he Bro.se !sers global permission is re&uired to search for groups in the 9rous
column! If you do not hae this permission, you will need to specify the e5act name of
the group:s;, followed by the #0nter# key after each group specified!
Remoing a group from a project role
4pen the Roles page!
+oer oer the 9rous column for the project role in which you are and click the yellow
bo5 which appears! "he users and groups will become editable!
%lick the E ne5t to the name of the group:s; you wish to remoe from this project role!
,e(ining a )omonent
%omponents are sub-sections of a project, used to group issues within a project into smaller
parts!
6anaging a project#s components
%hoose Administration at the top right of your screen! "hen choose $rojects from the
menu bar and select the name of the project of interest! 4therwise, choose your project
from the $rojects list or $roject %ategories!
"he $roject 'ummary page is displayed! "he %omponents section of the $roject
'ummary page shows a summary of components in your project!
%lick the? &oreK link to display the %omponents page, which shows a list of components
and each component#s details! 7rom here you can manage the project#s components as
described below!
Adding a new component
"he #Add %omponent# form is located at the top of the #%omponents# screen!
0nter the =ame for the component! 4ptionally enter a -escription and select a
%omponent 8ead and -efault Assignee
'electing a -efault Assignee
Jou can optionally set a -efault Assignee for a component! "his will oerride the project#s
default assignee, for issues in that component!
If an issue has multiple components, and the default assignees of components clash, the
assignee will be set to the default assignee of the component that is first alphabetically!
,e(ault Assignee
Otion
,es"rition
+ro2e"t ,e(ault Issues matching this component will hae the assignee set to the same
default assignee as the parent project
+ro2e"t 'ea$ "he assignee will be set to the project leader! :only if he is permitted to be
assigned issues in permission schemes;
)omonent 'ea$ "he assignee will be set to the component leader:only if he is permitted to
be assigned issues in permission schemes;
!nassigne$ "he assignee of the issue will not be set on the creation of this issue! "his
option will only be aailable if 2Allow unassigned issues2 is enabled in the
*eneral %onfiguration!
0diting a component#s details
4n the #%omponents# screen, hoer oer the releant component to display the pencil
icon!
"his will allow you to edit the component#s =ame, -escription, 8ead and -efault
Assignee!
%lick the #3pdate# button to sae your changes!
-eleting a component
4n the #%omponents# screen, hoer oer the releant component to display the #-elete#
button!
Jou will be prompted to associate these issues with another component if you wish!
&anaging Versions
<ersions are points-in-time for a project! "hey help you schedule and organize your releases!
4nce a ersion is created, and issues are assigned to it, the following reports are useful(
Road 6ap report D gies you a iew of upcoming ersions
%hange 8og report D gies you a reiew of released ersions
"he %hange 8og and Road 6ap reports are drien by the #7i5 for <ersion# field on each issue!
Versions "an 4e( Added, Released, Rescheduled, and 6erged D combine multiple ersions
into one!
6anaging a project#s ersions
%hoose Administration at the top right of your screen! "hen choose $rojects from the
menu bar and select the name of the project of interest!
"he <ersions section of the $roject 'ummary page shows a summary of ersions in
your project and the scheduled release date for each ersion!
%lick the 6ore link to display the <ersions page, which shows a list of ersions and each
ersion#s status! 7rom here you can manage the project#s ersions!
<ersion status( 0ach ersion can hae any of the following four statuses(
Release$ D a bundled package
!nrelease$ D an open package
Ar"hi%e$ D a semi-transparent package
O%er$ueD the release date is highlighted
Adding a new ersion
"he #Add <ersion# form is located at the top of the #<ersions# screen
0nter the name for the ersion! %lick the #Add# button!
"he ersion management list is updated immediately, with the newly created ersion
added at the top of the list D you can drag it to a different position if you wish, by
hoering oer the #drag# icon at the left of the ersion name!
Releasing a ersion
4n the GVersionsG screen, hoer oer the releant ersion to display the cog icon, then
select #Release# from the drop-down menu!
If there are any issues set with this ersion as their GFiE ForG ersion, JIRA allows you to
choose to change the GFiE ForG ersion if you wish! 4therwise, the operation will
complete without modifying these issues!
"o reert the release of a ersion, simply select G!nreleaseG from the drop-down menu!
If the JIRA is integrated with Atlassian#s /amboo, we can trigger a /amboo build to run
automatically when releasing a ersion in JIRA! "he ersion will only be released if the
build is successful!
Archiing a ersion
4n the #<ersions# screen, hoer oer the releant ersion to display the cog icon, then
select #Archie# from the drop-down menu!
"he ersion list indicates the ersion Gar"hi%e$G status with a semi-transparent icon! "he
list of aailable operations is replaced with the G!nar"hi%eG operation!
=o further changes can be made to this ersion unless it is un-archied! Also it is not
possible to remoe any e5isting archied ersions from an issue#s affected and fi5
ersion fields or add any new archied ersions!
"o reert the archie of a ersion, simply select G!nar"hi%eG from the drop-down menu!
6erging multiple ersions
It allows you to moe the issues from one or more ersions to another ersion!
4n the #<ersions# screen, click the #6erge# link at the top right of the screen!
"he #6erge <ersions# popup will be displayed!
4n this page are two select lists( both listing all un-archied ersions!
In the G&erging From VersionsG select list, choose the ersion:s; whose issues you
wish to moe!
<ersions selected on this list will be remoed from the system! All issues associated with
these ersions will be updated to reflect the new ersion selected in the G&erge To
VersionG select list!
It is only possible to select one ersion to merge to! %lick the G&ergeG button!
If you are shown a confirmation page, click G&ergeG again to complete the operation!
0diting a ersion#s details
4n the #<ersions# screen, hoer oer the releant ersion to display the pencil icon!
"his will allow you to edit the ersion#s =ame, -escription and Release -ate!
%lick the #3pdate# button to sae your changes!
-eleting a ersion
4n the #<ersions# screen, hoer oer the releant ersion to display the cog icon, then
select #-elete# from the drop-down menu!
"his will bring you to the 2-elete <ersion( R<ersionE2 confirmation page!
7rom here, you can specify the actions to be taken for issues associated with the ersion
to be deleted! Jou can either associate these issues with another ersion, or simply
remoe references to the ersion to be deleted!
Rescheduling a ersion
Rescheduling a ersion changes its place in the order of ersions!
4n the #<ersions# screen, click the icon for the releant ersion, and drag it to its new
position in the ersion order!
Running a Bam4oo Buil$ .hen Releasing a Version
=aigate to $rojects E the desired project E the desired ersion E Release tab!
If you are a JIRA administrator, ensure that you are not in #Administration# modeO
otherwise you will not see the controls described aboe!
Release the ersion! "he release build dialogue will be displayed!
0nter the build details for the release(
#=o /uild# ( if you do not want to run a /amboo build, only to release the ersion in
JIRA!
#Release new /uild#( to run a /amboo build that has not been started
#Release e5isting /uild#( to run a /amboo build that is in progress and has been
paused at an optional 'tage!
%lick the #Release# button! "he /amboo build will run! If it is successful, the JIRA ersion
will be released!
If not, you can choose to run it again or select a different $lan!
)reating Release Notes
JIRA proides the functionality to create release notes for a specific ersion of a project! "he
release notes contain all issues within the specified project that are marked with a specific
2FiE For2 ersion!
*enerating Release =otes
%hoose A$ministration at the top right of your screen!
"hen choose +ro2e"ts from the menu bar and select the name o( the ro2e"t of
interest! 4therwise, choose your project from the +ro2e"ts list or +ro2e"t
)ategories!
%lick GRoa$ &aG tab on the left of the screen!
.ip/ If you wish to see past release notes click on the 3)hange 4og3 tab instead.
%lick GRelease Notes# link for the project ersion whose release notes you wish to
generate!
"he GRelease NotesG page will be displayed!
%lick the G)on(igure Release NotesG link to configure the release notes!
"he G)on(igure Release NotesG page will be displayed(
'elect the re&uired project ersion for which the release notes will be generated in
the G+lease sele"t %ersionG dropdown!
'elect the re&uired format of the release notes D +"68 and plain te5t format
templates are proided in the G+lease sele"t styleG dropdown!
'electing the G)reateG button will generate the release notes using the specified
template in the specified format!
"he release notes will be displayed on screen and can be copied and pasted to
another application!
Adding a =ew 7ormat "emplate
%reate a <elocity template similar in content to that of the e5amples proided D
releasenotes-te5t!m and releasenotes-html!m!
"he title within the template should be modified along with the code within the te5t
area! "he other sections of the template do not need to be modified!
Add the new format template to the list of e5isting ones within the jira-
config!properties file! 7or each new template format, corresponding entries must be
added to the e5isting alues of the following properties(
jira!releasenotes!templatenames, jira!releasenotes!templates
S%orresponding entries in both of these properties must be in the same order!
If these properties do not e5ist in your jira-config!properties file, then for each of
these properties, add the property#s name, followed by an #T#, followed by the content
of the property#s corresponding Rdefault-alue>E element copied from your JIRA
installation#s jpm!5ml file!U =e5t, begin adding the corresponding entries for the new
format template!
"he new format template is aailable for selection as a release note format template!
)on(iguring Se"urity
When configuring security for your JIRA instance, there are two areas to address(
permissions within JIRA itself
security in the e5ternal enironment
%onfiguring permissions within JIRA
JIRA has a fle5ible security system which allows you to configure who can access JIRA, and
what they can do>see within JIRA!
"here are fie types of security within JIRA(
*lobal permissions D these apply to JIRA as a whole :e!g! who can log in;!
$roject permissions D organized into permission schemes, these apply to projects
as a whole :e!g! who can see the project#s issues, create, edit and assign them;!
Issue security leels D organized into security schemesO these allow the isibility of
indiidual issues to be adjusted, within the bounds of the project#s permissions!
%omment isibility D allows the isibility of indiidual comments :within an issue; to
be restricted!
Work-log isibility D allows the isibility of indiidual work-log entries :within an
issue; to be restricted! -oes not restrict isibility of progress bar on issue time
tracking!
%onfiguring security in the e5ternal enironment
If your JIRA instance contains sensitie information, you may want to configure security in the
enironment in which your JIRA instance is running! 'ome of the main areas to consider are(
-atabase( If you are using an e5ternal database as recommended for production
systems, you should restrict access to the database that your JIRA instance uses! If
you are using JIRA#s internal>bundled +'98 database, you should restrict access to
the directory in which you installed JIRA!
7ile system( you should restrict access to the following directories :Inde5 directory,
Attachments directory;
''8 D if you are running your JIRA instance oer the Internet, you may want to
consider using ''8!
)on(iguring Issue5le%el Se"urity
Issue security leels allow you to control who can see indiidual issues within a project!
A security leel#s members may consist of(
Indiidual users
*roups
$roject roles
Issue roles such as #Reporter#, #$roject 8ead#, and #%urrent Assignee#
#Anyone# :eg! to allow anonymous access;
A :multi-;user picker custom field!
A :multi-;group picker custom field! "his can either be an actual group picker custom
field, or a :multi-;select-list whose alues are group names!
Why use issue security leels.
As an e5ample, a company may hae a public instance of JIRA running! Within this instance
they may hae seeral projects that e5ternal people :customers; can browse! +oweer, it may
not be appropriate to show all issues to the customers! "o achiee this you could(
%reate an issue security scheme!
%reate an issue security leel named #$riate# for this scheme!
Add appropriate people to the #$riate# security leel!
Associate the issue security scheme with the releant projects!
'et the security leel of specific issues to #$riate#!
%reating an issue security scheme
%hoose Administration at the top right of your screen! "hen choose Issues E Issue
'ecurity 'chemes to open the #Issue 'ecurity 'chemes# page, which lists all the
issue security schemes currently aailable in your JIRA installation!
%lick the Add Issue 'ecurity 'cheme button!
In the Add Issue 'ecurity 'cheme form, enter a name for the issue security scheme,
and a short description of the scheme! "hen click the Add button!
Jou will return to the Issue 'ecurity 'chemes page, which now contains the newly
added scheme!
Adding a security leel to an issue security scheme
%lick the name of any scheme, or the link 'ecurity 8eels :in the 4perations column;
to open the 0dit Issue 'ecurity 8eels page!
In the Add 'ecurity 8eel bo5, enter a name and description for your new security
leel and then click Add 'ecurity 8eel!
'etting the -efault 'ecurity 8eel for an issue security scheme
%lick the name of any scheme or the link 'ecurity 8eels to open the 0dit Issue
'ecurity 8eels page!
"o set the #default# security leel for an issue security scheme, locate the appropriate
'ecurity
8eel and click its -efault link :in the 4perations column;!
"o remoe the #default# security leel from an issue security scheme, click the
#%hange default security leel to 2=one2# link :near the top of the page;!
Adding 3sers>*roups>$roject Roles to a 'ecurity 8eel
%lick the name of any scheme or the link 'ecurity 8eels to open the 0dit Issue
'ecurity 8eels page
8ocate the appropriate security leel and click its Add link :in the 4perations
column;, which opens the Add 3ser>*roup>$roject Role to Issue 'ecurity 8eel
page!
'elect the appropriate user, group or project role, then click the Add button!
Repeat steps G and H until all appropriate users and>or groups and>or project roles
hae been added to the security leel!
Assigning an issue security scheme to a project
%hoose Administration at the top right of your screen! "hen choose $rojects and
select the name of the project of interest! "he $roject 'ummary page is displayed!
In the $ermissions section of the $roject 'ummary page, click the link corresponding
to the Issues label to open the Associate Issue 'ecurity 'cheme to $roject page!
"his will either be the name of the project#s current issue security scheme, or
1NoneN!
'elect the issue security scheme that you want to associate with this project!
If there are no preiously secured issues :or if the project did not preiously hae an
issue security scheme;, skip the ne5t step!
If there are any preiously secured issues, select a new security leel to replace
each old leel! All issues with the security leel from the old scheme will now hae
the security leel from the new scheme! Jou can choose #=one# if you want the
security to be remoed from all preiously secured issues!
%lick the #Associate# button to associate the project with the issue security scheme!
-eleting an issue security scheme
%lick the -elete link :in the 4perations column; for the scheme that you want to
delete!
Jou cannot delete an issue security scheme if it is associated with a project! "o do
so, you must first remoe any associations between the issue security scheme and
projects in your JIRA installation!
4n the confirmation page, click -elete to confirm the deletion! 4therwise, click
%ancel!
%opying an issue security scheme
%lick the %opy link :in the 4perations column; for the scheme that you want to copy!
A new scheme will be created with the same security leels and the same
users>groups>project roles assigned to them!
9lo4al +ermissions an$ EElanations
JIRA System A$ministrators ( $ermission to perform all JIRA administration
functions! "his does not include the JIRA 3sers permission! A user with JIRA
'ystem Administrators will be able to log in to JIRA without the JIRA 3sers
permission, but may not be able to perform all regular user functions :e!g! edit their
profile; unless they also belong to a group that has the JIRA 3sers permission!
JIRA A$ministrators ( $ermission to perform most JIRA administration functions!
"his does not include the JIRA 3sers permission! A user with JIRA Administrators
will be able to log in to JIRA without the JIRA 3sers permission, but may not be able
to perform all regular user functions :e!g! edit their profile; unless they also belong to
a group that has the JIRA 3sers permission!
JIRA !sers ( $ermission to log in to JIRA! =ewly created users are automatically
assigned with this permission!
Bro.se !sers ( $ermission to iew a list of all JIRA user names and group names!
3sed for selecting users>groups in popup screens :such as the #3ser $icker#;!
0nables auto-completion of user names in the #3ser $icker# popup screen!
)reate Share$ O42e"ts ( $ermission to share a filter or dashboard globally or with
groups of users!
&anage 9rou Filter Su4s"ritions ( $ermission to manage :create and delete;
group filter subscriptions
Bul# )hange ( $ermission to e5ecute the bulk operations within JIRA( - /ulk 0dit >
6oe > Workflow "ransition> -elete
&anaging +ro2e"t +ermissions
$roject permissions are created within $ermission 'chemes, which are then assigned to
specific projects! $roject permissions can be granted to(
Indiidual users
*roups
$roject roles
Issue roles such as #Reporter#, #$roject 8ead# and #%urrent Assignee#
#Anyone# :e!g! to allow anonymous access;
A :multi-;user picker custom field!
A :multi-;group picker custom field!
$roject $ermissions and 05planations
+ermissions EElanations
A$minister +ro2e"ts $ermission to administer a project in JIRA, like edit project role
membership, project components, project ersions and some project
details
Bro.se +ro2e"ts $ermission to browse projects, use the Issue =aigator and iew
indiidual issues! &u"h other ermission is $een$ent on this
ermission, e!g! the #Work 4n Issues# permission is only effectie for
users who also hae the #/rowse $rojects# permission!
Vie. Issue Sour"e
Ta4
$ermission to iew the related source code commits : e!g! %<',
'ubersion, 7ish0ye, etc; for an issue, in a #'ource# tab!
Vie. 0Rea$5Only1
Wor#(lo.
$ermission to iew the project#s #read-only# workflow when iewing an
issue! "his permission proides the #<iew Workflow# link against the
#'tatus# field of the #<iew Issue# page!
Issue +ermissions EElanations
Assign Issues $ermission to assign issues to users
Assigna4le !ser $ermission to be assigned issues
)lose Issues $ermission to close issues
)reate Issues $ermission to create issues in the project! Includes sub-tasks
,elete Issues $ermission to delete issues
E$it Issues $ermission to edit issues > 'ub-tasks :e5cluding the #-ue -ate# field;
'in# Issues $ermission to link issues together
&o$i(y Reorter $ermission to modify the #Reporter# of an issue! "his allows a user to
create issues #on behalf of# someone else!
&o%e Issues $ermission to moe issues from one project to another or from one
workflow to another workflow within the same project! A user can only
moe issues to a project for which they hae %reate Issue permission!
Resol%e Issues $ermission to resole and reopen issues! "his also includes the ability
to set the #7i5 7or ersion# field for issues!
S"he$ule Issues $ermission to schedule an issue, i!e! 'et and edit the #-ue -ate# of an
issue!
Set Issue Se"urity $ermission to set the security leel on an issue to control who can
access the issue
Voters 7 Wat"hers
+ermissions
EElanations
&anage Wat"her 'ist $ermission to manage :i!e! iew>add>remoe users to>from; the
watcher list of an issue!
Vie. Voters an$
Wat"hers
$ermission to iew the oter list and watcher list of an issue!
)omments
+ermissions
EElanations
A$$ )omments $ermission to add comments to issues does not include the ability to
edit or delete comments!
,elete All )omments $ermission to delete any comments, regardless of who added them!
,elete O.n
)omments
$ermission to delete comments that were added by the user!
E$it All )omments $ermission to edit any comments, regardless of who added them!
E$it O.n )omments $ermission to edit comments that were added by the user!
Atta"hments
+ermissions
EElanations
)reate Atta"hments $ermission to attach files to an issue, does not include the ability to
delete attachments
,elete All
Atta"hments
$ermission to delete any attachments, regardless of who added them!
,elete O.n
Atta"hments
$ermission to delete attachments that were added by the user!
Time Tra"#ing
+ermissions
EElanations
Wor# On Issues $ermission to log work against an issue, i!e! create a worklog entry
,elete All Wor#logs $ermission to delete any worklog entries, regardless of who added
them
,elete O.n Wor#logs $ermission to delete worklog entries that were added by the user!!
E$it All Wor#logs $ermission to edit any worklog entries, regardless of who added
them!
E$it O.n Wor#logs $ermission to edit worklog entries that were added by the user

JIRA

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

JIRA

Transféré par

Droits d'auteur :

Formats disponibles

JIRA AN OVERVIEW

Vous aimerez peut-être aussi