JIRA Factory Default Settings

These factory defaults apply to JIRA version : 4.2.2

Installation Method

wget "http://www.atlassian.com/software/jira/downloads/binary/atlassian-jira-enterprise-4.2.2-b589-standalone.tar.gz"
tar -vzxf atlassian-jira-enterprise-4.2.2-b589-standalone.tar.gz 
# Download the Java JDK
# This link won't work you'll need to get a link from here : http://www.oracle.com/technetwork/java/javase/downloads/index.html
wget "http://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/VerifyItem-Start/jdk-6u24-linux-i586-rpm.bin?BundledLineItemUUID=7CeJ_hCyUi4AAAEuavkIR1m_&OrderID=ZaiJ_hCyAAEAAAEuUPkIR1m_&ProductID=xpeJ_hCwsEQAAAEtAMoADqmS&FileName=/jdk-6u24-linux-i586-rpm.bin"
chmod 755 jdk-6u24-linux-i586-rpm.bin 
./jdk-6u24-linux-i586-rpm.bin 
export JAVA_HOME=/usr/java/jdk1.6.0_24
mkdir /opt/jira
patch -p0 <<EOF
--- atlassian-jira-enterprise-4.2.2-b589-standalone/atlassian-jira/WEB-INF/classes/jira-application.properties.orig	2011-02-24 15:27:05.000000000 -0800
+++ atlassian-jira-enterprise-4.2.2-b589-standalone/atlassian-jira/WEB-INF/classes/jira-application.properties	2011-02-24 14:28:12.000000000 -0800
@@ -15,7 +15,8 @@
 #
 # You can also use Unix-like paths which Java/JIRA can handle, eg c:/jira/home
 #
-jira.home =
+#jira.home =
+jira.home = /opt/jira
 
 ########################################################################################################################
 #
EOF
atlassian-jira-enterprise-4.2.2-b589-standalone/bin/startup.sh

Required Customization

These are the things for which there is no default. These are the values that I've used in my example

  • Username : admin
  • Project Name : Factory Default Project
  • Key : FAC

Factory Default Project

Project: Factory Default Project
Key: FAC
URL: No URL
Project Team:
Project Lead: admin
Default Assignee: Project Lead
Project Roles: View members
Issue Type Scheme: Default Issue Type Scheme ( Select | Edit | Manage )
Notification Scheme: Default Notification Scheme ( Select | Edit )
Permission Scheme: Default Permission Scheme ( Select | Edit )
Issue Security Scheme: None ( Select )
Field Configuration Scheme: System Default Field Configuration
Issue Type Screen Scheme: Default Issue Type Screen Scheme ( Select | Edit )
Workflow Scheme: None ( Select )
CVS Modules: None ( Select Modules )
Project Category: None ( Select Category )

Default Issue Type Scheme

  • Description : Default issue type scheme is the list of global issue types. All newly created issue types will automatically be added to this scheme.
  • Default Issue Type : Bug
    • Bug
    • New Feature
    • Task
    • Improvement
    • Sub-task (sub-task)

Default Notification Scheme

Event Notifications Operations
Issue Created (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Issue Updated (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Issue Assigned (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Issue Resolved (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Issue Closed (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Issue Commented (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Issue Comment Edited (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Issue Reopened (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Issue Deleted (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Issue Moved (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Work Logged On Issue (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Work Started On Issue (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Work Stopped On Issue (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Issue Worklog Updated (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Issue Worklog Deleted (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add
Generic Event (System) "Current Assignee (Delete)
Reporter (Delete)
All Watchers (Delete)"
Add

Default Permission Scheme

Project Permissions Users / Groups / Project Roles Operations
Administer Projects
Ability to administer a project in JIRA.
Project Role (Administrators) (Delete) Add
Browse Projects
Ability to browse projects and the issues within them.
Project Role (Users) (Delete) Add
View Version Control
Ability to view Version Control commit information for issues.
Project Role (Developers) (Delete) Add
Issue Permissions Users / Groups / Project Roles Operations
Create Issues
Ability to create issues.
Project Role (Users) (Delete) Add
Edit Issues
Ability to edit issues.
Project Role (Developers) (Delete) Add
Schedule Issues
Ability to set or edit an issue's due date.
Project Role (Developers) (Delete) Add
Move Issues
Ability to move issues between projects or between workflows of the same project (if applicable). Note the user can only move issues to a project he or she has the create permission for.
Project Role (Developers) (Delete) Add
Assign Issues
Ability to assign issues to other people.
Project Role (Developers) (Delete) Add
Assignable User
Users with this permission may be assigned to issues.
Project Role (Developers) (Delete) Add
Resolve Issues
Ability to resolve and reopen issues. This includes the ability to set a fix version.
Project Role (Developers) (Delete) Add
Close Issues
Ability to close issues. Often useful where your developers resolve issues, and a QA department closes them.
Project Role (Developers) (Delete) Add
Modify Reporter
Ability to modify the reporter when creating or editing an issue.
Project Role (Administrators) (Delete) Add
Delete Issues
Ability to delete issues.
Project Role (Administrators) (Delete) Add
Link Issues
Ability to link issues together and create linked issues. Only useful if issue linking is turned on.
Project Role (Developers) (Delete) Add
Set Issue Security
Ability to set the level of security on an issue so that only people in that security level can see the issue.
  Add
Voters & Watchers Permissions Users / Groups / Project Roles Operations
View Voters and Watchers
Ability to view the voters and watchers of an issue.
Project Role (Developers) (Delete) Add
Manage Watchers
Ability to manage the watchers of an issue.
Project Role (Administrators) (Delete) Add
Comments Permissions Users / Groups / Project Roles Operations
Add Comments
Ability to comment on issues.
Project Role (Users) (Delete) Add
Edit All Comments
Ability to edit all comments made on issues.
Project Role (Developers) (Delete) Add
Edit Own Comments
Ability to edit own comments made on issues.
Project Role (Users) (Delete) Add
Delete All Comments
Ability to delete all comments made on issues.
Project Role (Administrators) (Delete) Add
Delete Own Comments
Ability to delete own comments made on issues.
Project Role (Users) (Delete) Add
Attachments Permissions Users / Groups / Project Roles Operations
Create Attachments
Users with this permission may create attachments.
Project Role (Users) (Delete) Add
Delete All Attachments
Users with this permission may delete all attachments.
Project Role (Administrators) (Delete) Add
Delete Own Attachments
Users with this permission may delete own attachments.
Project Role (Users) (Delete) Add
Time Tracking Permissions Users / Groups / Project Roles Operations
Work On Issues
Ability to log work done against an issue. Only useful if Time Tracking is turned on.
Project Role (Developers) (Delete) Add
Edit Own Worklogs
Ability to edit own worklogs made on issues.
Project Role (Users) (Delete) Add
Edit All Worklogs
Ability to edit all worklogs made on issues.
Project Role (Developers) (Delete) Add
Delete Own Worklogs
Ability to delete own worklogs made on issues.
Project Role (Users) (Delete) Add
Delete All Worklogs
Ability to delete all worklogs made on issues.
Project Role (Administrators) (Delete) Add

System Default Field Configuration / Default Field Configuration

Name Screens Operations
Affects Version/s
[Autocomplete Renderer]
Default Screen Edit | Hide | Required | Screens | Renderers
Assignee Default Screen
Resolve Issue Screen
Workflow Screen
Edit | Hide | Screens
Attachment Default Screen Edit | Hide | Screens
Comment
[Wiki Style Renderer]
This field can not be placed on screens by users. Edit | Renderers
Component/s
[Autocomplete Renderer]
Default Screen Edit | Hide | Required | Screens | Renderers
Description
[Wiki Style Renderer]
Default Screen Edit | Hide | Required | Screens | Renderers
Due Date Default Screen Edit | Hide | Required | Screens
Environment
[Wiki Style Renderer]
For example operating system, software platform and/or hardware specifications (include as appropriate for the issue).
Default Screen Edit | Hide | Required | Screens | Renderers
Fix Version/s
[Autocomplete Renderer]
Default Screen
Resolve Issue Screen
Edit | Hide | Required | Screens | Renderers
Issue Type (Required) Default Screen Edit | Screens
Labels Default Screen Edit | Hide | Required | Screens
Log Work
[Wiki Style Renderer]
Allows work to be logged whilst creating, editing or transitioning issues.
Resolve Issue Screen Edit | Hide | Required | Screens | Renderers
Priority Default Screen Edit | Hide | Required | Screens
Reporter (Required) Default Screen Edit | Hide | Optional | Screens
Resolution Resolve Issue Screen Edit | Hide | Screens
Security Level Default Screen Edit | Hide | Required | Screens
Summary (Required) Default Screen Edit | Screens
Time Tracking
An estimate of how much work remains until this issue will be resolved.
The format of this is ' *w *d *h *m ' (representing weeks, days, hours and minutes - where can be any number)
Examples: 4d, 5h 30m, 60m and 3w.
Default Screen Edit | Hide | Required | Screens

Screens

Default Screen

Position Name
1 Summary
2 Issue Type
3 Security Level
4 Priority
5 Due Date
6 Component/s
7 Affects Version/s
8 Fix Version/s
9 Assignee
10 Reporter
11 Environment
12 Description
13 Time Tracking
14 Attachment
15 Labels

Resolve Issue Screen

Position Name
1 Resolution
2 Fix Version/s
3 Assignee
4 Log Work

Workflow Screen

Position Name
1 Assignee

Default Issue Type Screen Scheme

Issue Type Screen Scheme
Default
Used for all unmapped issue types.
Default Screen Scheme

Default Screen Scheme

Issue Operation Screen
Default
Used for all unmapped operations.
Default Screen

Workflows

Name Description Status Schemes Number of steps Operations
jira (Read-only System Workflow) The default JIRA workflow. Active Used by projects with no associated workflow scheme and by workflow schemes with unassigned issue types. 5 Steps | XML | Copy

Project Roles

Project Role Name Description
Administrators A project role that represents administrators in a project
Developers A project role that represents developers in a project
Users A project role that represents users in a project

Issue Types

Name Description Type
Bug A problem which impairs or prevents the functions of the product. Standard
Improvement An improvement or enhancement to an existing feature or task. Standard
New Feature A new feature of the product, which has yet to be developed. Standard
Task A task that needs to be done. Standard
Sub-task The sub-task of the issue Sub-Task

Priorities

Name Description
Blocker Blocks development and/or testing work, production could not run.
Critical Crashes, loss of data, severe memory leak.
Major Major loss of function.
Minor Minor loss of function, or other problem where easy workaround is present.
Trivial Cosmetic problem like misspelt words or misaligned text.

Resolutions

Name Description
Fixed (Default) A fix for this issue is checked into the tree and tested.
Won't Fix The problem described is an issue which will never be fixed.
Duplicate The problem is a duplicate of an existing issue.
Incomplete The problem is not completely described.
Cannot Reproduce All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.

Statuses

Status Details Mode
Open
The issue is open and ready for the assignee to start work on it.
Active
In Progress
This issue is being actively worked on at the moment by the assignee.
Active
Reopened
This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
Active
Resolved
A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
Active
Closed
The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
Active

Greenhopper

By enabling Greenhopper with the default "Scrum" template for a project the following settings are changed :

  • Issue Type Scheme: GreenHopper Scrum Issue Type Scheme ( Select | Edit | Manage )
  • New Custom Fields are created
  • New Issue Types are created
  • The "Default Issue Type Scheme" has the newly created Issue Types added to it

GreenHopper Scrum Issue Type Scheme

  • Description : This issue type scheme is used by GreenHopper's Scrum project template. Projects associated with the Scrum template will be associated to this scheme. You can modify this scheme.
  • Default Issue Type : Story
    • Epic
    • Story
    • Technical Task (sub-task)
    • Bug
    • Improvement

GreenHopper New Custom Fields

Name Type Available Context(s)
Business Value
Measurement of business value of a requirement.
Number Field Issue type(s): Epic | Story
Epic/Theme
Field that will help you regroup issues under an Epic or under a theme.
Labels Global (all issues)
Flagged
Allows to flag issues with impediments.
Multi Checkboxes Global (all issues)
Rank
The ranking field will help in organizing and prioritizing your issues/cards in your product/sprint backlog more effectively.
GreenHopper Ranking Global (all issues)
Release Version History
The released versions an incomplete issue has been in when it was forwarded to the next sprint
GreenHopper Released Version History Global (all issues)
Story Points
Measurement of complexity and/or size of a requirement.
Number Field Issue type(s): Epic Story

GreenHopper New Issue Types

Issue Types

Name Description Type
Epic A big user story that needs to be broken down. Standard
Story An user story Standard
Technical task A technical task. Sub-Task

Default Issue Type Scheme after GreenHopper modification

  • Description : Default issue type scheme is the list of global issue types. All newly created issue types will automatically be added to this scheme.
  • Default Issue Type : Bug
    • Bug
    • New Feature
    • Task
    • Improvement
    • Sub-task (sub-task)
    • Epic
    • Story
    • Technical Task (sub-task)
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.