JIRA applications sample file - Project Management
This sample file is out of date. Related information available on the JIRA Project Management Feature Product Tour.
JIRA applications for Project Management sample file
What is a sample file? A sample file is an example setup - a sandbox environment designed to give you an overview of some of the popular and useful features. You can restore this backup file into your JIRA applications instance (download the free 30-day trial if you haven't already) and play around in the system.
JIRA applications for Project Management sample file is an example of how to use JIRA application to manage some common internal processes - purchasing, recruiting, marketing, and building a product. There are a several users separated into teams and different levels within the company. You can switch between users to see different views of the system. You can create and work with issues - blog entries, tasks, sales positions and more - move the issues through their respective steps, pull reports on issues and activity, and explore the features that Project Managers use within JIRA applications.
Note this is just one example of many ways you can use JIRA applications to manage projects. If you have questions or would like to discuss your organisation processes in more detail, don't hesitate to email or call Atlassian Sales.
Before using the sample file...
- Please back up your existing JIRA applications instance. You can read how to do this here. Note that when you restore this sample file into your instance, you'll wipe out any existing data.
- The latest sample file was created using JIRA 4.4.3, please ensure you have this version.
You can download the latest version of JIRA applications here. - You will also need to download two plugins for all the features to work properly.
Follow the instructions for each plugin.- The plugins you will need are:
Download the sample file
- Please ensure you have backed up your existing JIRA instance.
- Before you download the sample file please ensure you know how to restore it.
- You can download the sample file here!
Project Management sample file features
- Based on using JIRA applications to track projects for several departments at one company
- 10 users - you can jump to another user by clicking their name in the top bar - all users have the password 'password'.
- Several system and project specific dashboards
- 4 workflows, including some common customizations
- Parents task cannot be closed unless all subtasks are closed (Plane workflow)
- Certain transitions can only be executed by managers (Make Offer in Recruitment workflow; Approve or Deny in Purchasing workflow)
- Permissions are the same for marketing, plane, and purchasing
- permissions restricted only to project lead Sarah [JIRA:HR] and Managers for Recruitment project (note JIRA application Administrator can browse and administer project, but doesn't have permission for operations)
- Two issue security levels within the Recruitment project: Project Lead + All Managers, Project Lead + Reporter
Tour of the sample file
This brief walk-through is designed to give you a feel for how information flows within JIRA applications, how different users view and work with the same information (permission based operations) and show you some common features project managers find useful within JIRA applications.
Click on each arrow to open up the example issue and follow the screenshots.
Let's start by creating a few issues.
Now, let's pull some reports on what we've just done.
Enhancing the sample file
Now that we've created some issues, explored some favorite features, and played with some reports, go ahead and build upon the system.
You can explore project permissions, set up JIRA application to send outgoing and create issue and comments from incoming emails, and set up notifications.
If you want to customize a workflow to match your own internal processes, take a look at the short workflow demo video and follow the JIRA Quick Start Guide.
Finally, you can customize the look and feel, migrate your own data into JIRA application, and follow the JIRA applications docs to explore other features.
Other recommended plugins
- JIRA Suite Utilities - This plugin is divided in two parts. First, a set of conditions and validations to personalize workflow of JIRA. And second, a Issue Tab Panel, which shows information about the execution of each transition. The nice addition - custom fields for specifying Google Maps location.* Custom Fields
- JIRA Toolkit - The toolkit is a set of neat custom fields Atlassian developed for our own use. They provide a simple workaround for current limitations to JIRA or solutions to some idiosyncratic problems. Think of it as JIRA Custom fields sandbox if you will. It's also a showcase for how simple custom fields can be used get more out of your of JIRA, especially for filtering on information that would otherwise be unavailable.
- Links Hierarchy Reports - This plugin is an interactive hierarchical view of linked Issues based on a selected link type.
- JIRA Labels plugin - Allows you to tag your issues with arbitrary labels - especially helpful for teams within teams, labels that will function cross-project, and any terminology or lingo that your organization uses internally.
Project Details
Marketing Project details (MKT)
- Project Roles
- Project lead: Joshua [JIRA:sales manager]
- issue types
- case study
- website content
- blog entry
- improvement
- task
- subtask
- components
- blogs
- product content
- company content
- external site
- versions - Q1, Q2, Q3, Q4
- workflow:
Purchasing Project details (PUR)
- Project Roles
- Project Lead: Sammy [JIRA:purchasing manager]
- issue types
- purchasing request
- * workflow with escalation (for additional approvals):
- Only users in the Project Role 'Managers' can transition this step:
- Purchase Workflow
- Only users in the Group Purchasing can approve requests in the initially.
- Requests can be escalated to managers, and then only people in the Managers Project Role can approve the request.
Recruitment Project details (RCMT)
- Project Roles
- Sarah [JIRA:HR]
- issue types
- technical sales position
- marketing position
- developer position
- Create issue screen
- summary
- description
- attachment
- priority
- date needed
- components - San Francisco, Sydney, Amsterdam
- versions - Q1, Q2, Q3, Q4
- Only users in the Project Role 'Managers' can transition to 'Make Offer' step
- * workflow to track all potential hires - Where are they in the process? Who did the phone interview? Did they reject the offer? Did they give a reason why?:
Plane Project details (PLN)
- Project Roles
- Project Lead: Christina [JIRA:admin]
- issue types
- task
- improvement
- workflow: same as JIRA default but added subtask blocking condition for 'Resolve Issue' and 'Close Issue' transitions:
Further Resources
Contact us
Looking for something that is not listed here? Simply contact us and we'll gladly help you out.