...
Quick search | The quick search is the fastest way to define search criteria. However, it is less precise than other search methods for complex queries (e.g. To use the quick search: Enter your search criteria in the search box in the header bar of Jira and press Enter. More detailed information can be found on the following Atlassian page: Quick searching | ||||||
---|---|---|---|---|---|---|---|
Basic search | The basic search is more precise than the quick search, but easier to use than the advanced search. To use the basic search: Navigate to Issues (in header) > Search for issues, then enter your search criteria. | ||||||
Advanced search | The advanced search is the most powerful of the three search methods. You can specify criteria that cannot be defined in the other searches (e.g. To use the advanced search: Navigate to Issues (in header) > Search for issues, then enter your search criteria.
Searching for flagged issuesThe flag for an issue is stored in a custom checkbox field named "Flagged", which has only one value: Impediment. This means that you can use this JQL query to find flagged issues: |
The Jira Issue search functionality search functionality is enhanced by the ability to save searches, called filters in Jira, for later use.
More detailed information how to work with filters can be found on the following Atlassian page: Saving your search as a filter
Please note that a filter can be shared with other users. You can share a filter with:
Project: All members or members with specific project roles working on one or multiple projects.
Group: A group of Jira users.
Open: Any user who is logged-in to your Jira Cloud site.
Public: Public sharing means sharing the dashboard with users who are not logged in to your Jira site. Note that if you share a filter publicly, it will be visible and searchable on the internet.
Private: Only you can view the filter.
Filters can also be used in Dashboards to show a result. Instructions how to do can be found here Editing dashboards.
...
Versions are points-in-time for a project. They help you schedule and organize your releases.
Once a version is created and issues are assigned to it, you can use several reports, e.g. the Change Log report, when managing the version.
The Change Log report, in particular, gives you a review of the released version, and is driven by the 'Fix For Version' field on each issue.
Versions can only be managed when you have Project administrator or Jira Admin permission including Edit issue permission.
At YME we use an Addon for Version management called Version manager so users without Project administrator or Jira administrator permissions can also use this functionality.
Versions set via via Manage versions can can be selected via drop-down fields 'Fix Version/s' and 'Affects Version'.
...
A version is a set of features and fixes released together as a single update to your product. By default, Kanban boards do not require issues to be pre-assigned to versions. This is because Kanban is designed for a continuous flow of work, rather than set iterations.
On a Kanban board, you can choose to release a version at any point in time — the version will contain all issues that are complete at that time. You also specify the name of a new version at the time of the release.
For information on how to release a version on a Kanban board, see Deploying a release.
If your team is using the Kanban backlog for your Kanban project, you can use the Versions panel to manage versions.
...
Note |
---|
Dashboard Hub for Jira is running on a trial license and is currently being tested if this meet the requirements for agile metric reporting. |
Create and share powerful dashboards effortlessly for ITSM, Agile, DevOps teams. Use templates, ~100 advanced gadgets, custom charts, and 12+ integrations
...