|
JIRA Documentation
|
Usage FAQ
- Adding a Review Step to The Workflow (Draft) — How to add a Review step to your JIRA workflow. This document will show you how to create/edit a workflow that will contain a extra step for review and notify the appropriate parties via e-mail. The ability to edit workflows is only available in the JIRA Professional and Enterprise versions.
- Adding custom content to the front page
- Advanced JIRA configuration with jira-application.properties — jira-application.properties contains other properties which are not editable from the web interface. Usually these are of little interest to most users, but sometimes you may wish to edit them.
- Allow editing of Closed Issues
- Allowing users to create issues anonymously
- Anonymising data
- Asking for an attachment on the Create Issue page
- Associating a new screen with issue operations — When you spend some quality time creating a new screen with custom fields, you want to make people use it. This quick and dirty how-to helps make your screen implementation dreams come true!
- Can I store customer details, like company, address and contact information, in JIRA?
- Changing Custom Field Types
- Changing JIRA's log output — A common task when identifying JIRA problems is to turn up the log level, to get more debug-level logs.
- Changing the default attachment size limit
- Changing the default session timeout
- Changing the Due Date input format
- Changing the Issue Key format
- Changing the Project Key
- Changing the username in Jira
- Commonly Asked CSV Questions and Known Issues
- Configuring project specific security
- Controlling project visibility
- Creating an Unassigned Issue
- Creating Issues via direct HTML links
- Current Reporter Browse Project Permission
- CVS ssh Jira Integration
- Deleting a user account
- Downgrading JIRA
- Editing a custom field option
- Editing the work log
- Escalating issues (or sending email notifications) when the set turnaround time is exceeded
- Extra CSV Import Features
- Field Layout Schemes in JIRA 3.x
- Group Name Guidelines for JIRA
- How is JIRA pronounced?
- How the CreateOrCommentHandler works?
- Importing data
- Importing user from LDAP
- International characters in notification email subjects
- JIRA and SSL
- Connecting to SSL services
- Running JIRA over SSL or HTTPS — When web applications are being accessed across the internet, there is always the possibility of usernames and passwords being intercepted by intermediaries (e.g. between your computer and the ISP/company). It is often a good idea to enable access via HTTPS (HTTP over SSL), and require its use for pages where passwords are sent. Note, however, that using HTTPS may result in slower performance.
- JIRA as a Project Management Tool
- JIRA as a Support System
- JIRA Quick Start Guide
- JIRA Sample File - General uses
- JIRA Sample File - Helpdesk or Support System
- JIRA Standalone quick source modifications
- Letting customers only create issues — This page describes a minor JIRA modification which redirects users to an arbitrary page after creating issues (and potentially other operations). It is mainly of interest to JIRA Professional and Standard users.
- Limiting the number of issues returned from a search view such as an RSS feed
- Linking to local file under Firefox
- Login problems
- Mail error - Unable to relay
- Merging 2 JIRA instances
- Obsolete guides — Administration guides applying to older versions of JIRA
- Outward Link Description and Inward Link Description
- Parsing utf-7 emails
- Plans for JIRA's LDAP integration
- Project-specific email templates
- QuickSearch guesses the issue key prefix (sometimes)
- Retrieving the JIRA Administrator's password
- Scheme Entity Relations Map — This diagram illustrates the relationships between various JIRA entities (Enterprise Edition) and schemes.
- Sending a JIRA data backup to support
- Translating JIRA
- Troubleshooting Issue Creation Via Email — Use this excerpt to provide a brief explanation of what this how-to will do.
- Updating your JIRA License Details
- User access logging — How to track user actions with page access logging
- Using Issue Level Security with Project Roles — This tutorial (for JIRA Enterprise Customers) provides a step-by-step guide for creating project roles and using them in an issue security scheme. We recommend creating a test project and two test users for this tutorial.
- Using JIRA to Manage reusable modules
- Using validators to make custom fields required on transition screens — It is currently not possible to make a field mandatory on any transition screen.The following Workflow Validator Extension is an example of how a user can use their custom field(s) to validate against in order to make these fields required on their associated transition screen.
- We already have users & groups defined elsewhere - can JIRA make use of these?
- What are the differences between JIRA Enterprise, Professional and Standard editions?
- What does JIRA mean?
- Where are the JIRA logs? — A decision tree for finding JIRA logs on your system
- Why doesn't JIRA have a Severity field like Bugzilla?
- Words ignored when searching
- XML format for import & export files
|
Adding a Review Step to The Workflow (Draft)