Jira Interview Questions

By YuwebDesign

software used to help manage, develop and communicate about projects

These can be team or individual projects,
that can have a various level of complexity.

Jira is mainly used for Agile, but can also be used with Waterfall.

Jira Hierarchy
Jira is organized around the hierarchy.

  1. Highest level is application level: Jira (a collection of projects)
    When you log in to Jira using your browser, you are usually at the application level.
    At application level you can see Projects tab on the blue sidebar.
    You can access application level by clicking Jira icon on the top left of the blue sidebar.
  2. Project level: A project (a collection of issues)
    View a collection of projects by clicking Projects tab in the blue sidebar ->
    click on the specific project to move to the project level of the hierarchy.
  3. Issue level: An issue (work item)
    Once you have navigated to a specific project, you can view a list of its issues.

An issue
can represent any work that needs to be done in a project,
e.g., a specific feature that you are building for a product.

Classic: all the power and traditional Jira functionality you expect.
Created and managed by your Jira admin.
In general they are more mature and have more functionality
than next generation projects,
they have more configuration capabilities,
and configurations can be shared among multiple projects
Next Gen: are newer to Jira
capabilities are being added in an Agile way.
In general, you will see more changes to next generation projects than to classic projects.
Created and managed by project team members.

Start by making sure you are at the Jira application level.
-> click on the Projects tab
-> create project
Enter a project name -> Optionally change the project template
(Kanban Scrum Bug tracking Project management Task tracking Process control
you can change the configuration of your project at any time)
-> click Create to create a project

Click on a plus side on a global sidebar
-> enter issue details (you can add more details later)
-> click on create to create a project

Issue Key
Jira automatically assigns a unique issue key to created issues
issue_key = project_key-issue_number
E.g., PRJCT2-1
Issue key values are unique to the Jira account,
you can not have two projects with the same project key

There is a hierarchy of settings in Jira that maps to the levels

contextual sidebar – application level settings
Changing settings at the application applies to all projects
available to Jira administrators, users with less permissions will not have access to these settings

Contextual sidebar – Project level settings
Clicking on Project Settings while inside of a project applies only to that project

Site level

Leave a Reply or Comment

Your email address will not be published. Required fields are marked *