What is the difference between a global workflow and a project-specific workflow in JIRA?
- A global workflow allows more customization options than a project-specific workflow.
- A global workflow applies to all projects in JIRA, while a project-specific workflow is tailored to a specific project.
- A global workflow is managed by project administrators, while a project-specific workflow is managed by system administrators.
- A project-specific workflow can be shared between multiple projects, whereas a global workflow cannot.
In JIRA, a global workflow applies universally to all projects within the instance, ensuring consistency across projects. On the other hand, project-specific workflows are tailored to the needs of individual projects, allowing for greater flexibility and customization based on project requirements.
Issue naming conventions help users quickly understand the _______ of a JIRA issue.
- Category
- Priority
- Purpose
- Status
Clear issue names in JIRA assist users in quickly grasping the importance or significance of the issue, aiding in prioritization and decision-making.
Scenario: You have been assigned as the project lead for a critical project in JIRA. What are your responsibilities, and how can you manage the project effectively?
- Attend meetings without actively participating
- Define project goals, timelines, and deliverables
- Delegate all tasks to team members
- Ignore project risks and issues
As the project lead for a critical project in JIRA, your responsibilities include defining project goals, timelines, and deliverables, ensuring clarity and alignment among team members. Effective project management involves active participation in meetings to provide guidance, resolve issues, and make informed decisions. Ignoring project risks and issues can lead to delays and setbacks. Delegating tasks to team members is essential, but the project lead should also maintain oversight and accountability.
What are the different types of issue links available in JIRA?
- Blocks, Clones, Relates, Duplicate
- Blocks, Relates, Duplicate, Is cloned by
- Clones, Relates, Depends on, Duplicates
- Relates, Clones, Is blocked by, Duplicates
The different types of issue links available in JIRA are: Blocks, Clones, Relates, and Duplicates. These links help establish relationships between different issues, such as indicating that one issue blocks another, or that two issues are duplicates of each other.
Your team is considering implementing JIRA Data Center for high availability and scalability. What key components and architecture changes should you plan for in this setup?
- Caching mechanisms, Single-server setup, Increased RAM allocation, Web browser compatibility improvements
- Enhanced user interface, Third-party integrations, Database schema optimization, Increased network bandwidth
- Incremental backups, JIRA service desk, Agile project management, Kanban boards
- Load balancer, Shared file system, Database replication, Clustering
Implementing JIRA Data Center involves key components like load balancer for distributing traffic, shared file system for shared data storage, database replication for data synchronization, and clustering for high availability. These architectural changes are essential for achieving scalability and ensuring uninterrupted service.
When creating a new issue type in JIRA, you can define custom _______ to capture specific information.
- Epics
- Fields
- Priorities
- Workflows
When creating a new issue type in JIRA, administrators have the ability to define custom fields. These custom fields can capture specific information relevant to the new issue type, allowing for greater flexibility and customization within the JIRA instance.
How can you create a new Automation Rule in JIRA?
- By installing third-party plugins.
- By modifying the JIRA source code directly.
- By navigating to the Project Settings > Automation and creating a new rule from there.
- By requesting assistance from JIRA support team.
You can create a new Automation Rule in JIRA by accessing the Project Settings, then selecting Automation, and finally creating a new rule from there. This allows users to define the conditions and actions for their automation rules without needing to modify the JIRA source code or seek external support.
In JIRA, an issue can have one or more _______ assigned to it.
- Assignees
- Labels
- Roles
- Users
In JIRA, an issue can have one or more assignees assigned to it. Assignees are individuals responsible for working on the issue. Multiple assignees can be assigned to an issue to distribute work among team members efficiently.
In Agile, the product backlog is a prioritized list of _______.
- Features
- Requirements
- Tasks
- User Stories
In Agile methodology, the product backlog consists of user stories, which are concise descriptions of desired functionality from an end user's perspective, prioritized based on business value.
To automate repetitive tasks in JIRA, you can use _______ to trigger actions based on specific events.
- Conditions
- Events
- Rules
- Triggers
Triggers in JIRA Automation are used to initiate actions when certain events occur. These events could include issue creation, transition, or comment addition, among others. Rules encompass both conditions and actions, where conditions define when the rule should execute, and actions specify what tasks should be performed.