Using macros helps you to expand the capabilities of your Confluence pages, allowing you to add extra functionality or include dynamic content. Let’s take a look at some project characteristics that can only be altered by JIRA global administrators: Issue types Workflows Screens Fields Permissions Issue Security Notifications Contact a JIRA administrator if you need any customization, specially when requesting a new JIRA Project Visitors to your web site do not require a user account in JIRA to use the JIRA feedback form. When people visiting your web site click this trigger tab and submit the resulting JIRA feedback form, an issue is conveniently created in JIRA.

This form is typically accessed by clicking a 'trigger' tab exposed along the edge of pages in your web site.

The issue collector allows you to easily embed a JIRA feedback form into your own web site. Since these links are project-specific, you can set them up to provide shortcuts for pages a project team uses frequently.ġ8 JIRA – Project Administration Issue Collectors These appear in a pop-up window that opens when you click the project avatar in JIRA or Confluence. This will override the project's default assignee, for issues in that component.ġ7 JIRA – Project Administration Team shortcuts Note that you can set a Default Assignee for a component. They are used to group issues within a project into smaller parts. Each version can have any of the following four statuses: Released - a bundled package Unreleased - an open package Archived - a semi-transparent package Overdue- the release date is highlightedġ6 JIRA – Project Administration ComponentsĬomponents are sub-sections of a project. Merged: combine multiple versions into one. Archived: hide an old version from the Road Map and Change Log reports, and in the JIRA User Interface. Rescheduled: re-arrange the order of versions. This changes the Road Map report, Change Log report and some issue fields' drop-downs. Versions can be: Added: create a new version against which issues can be aligned. They help you schedule and organize your releases. Versions are points-in-time for a project.

Project roles are somewhat similar to groups, the main difference being that group membership is global whereas project role membership is project-specific.ġ5 JIRA – Project Administration Versions

There are 3 defined Project Roles: Administrator: People who administer the project Developer: People who work on issues in the project User: People who log issues in the project Check the permissions assigned to each role in the Permissions section. Project administrators assign members to project roles specifically for their project. What a project Administrator can manage: Roles Versions Components Team shortcuts Issue Collectors Saved queries Sharing control: Permissions reports: Subscriptions Run a query on a scheduled basis and the result to you or a group of people. One more thing! To search all text fields (summary, description, comments, etc) in JIRA at once: text ~ 'Search Text” One more one more thing: JQL can by used with the RESTful interface to do awesome stuff… Common operators include equals (=), not equals (!=), less than ( -2w ORDER BY created DESC In JIRA fields can include: priority, fixVersion, issue type, etc. JQL = JIRA Query Language Syntax similar to SQL, however, JQL is not a database query language Complete reference: But if you are not familiar with SQL queries, this is the right presentation for you!įields hold different types of information in the system. JQL Filters Project administration Roles Versions Components Team Shortcuts Issue Collectors Confluence Advanced editing Macros JIRA reports Space administration Create a space Sidebar configuration Permissions Templates Leandro Fernández & Iñigo Alonso ICS November 7, 2014Ģ Index JIRA Confluence Advanced search Advanced editing

Confluence roadmap planner widget