What is the difference between a global workflow and a project-specific workflow in JIRA?
- A global workflow is only used for certain issue types, while a project-specific workflow is used for all issue types.
- A global workflow is shared across all projects, while a project-specific workflow is tailored to a particular project.
- A global workflow is specific to a project, while a project-specific workflow is shared across all projects.
- A global workflow is used only for administrative purposes, while a project-specific workflow is used for operational tasks.
A global workflow in JIRA is shared across all projects, ensuring consistency in workflow management across the JIRA instance. Conversely, a project-specific workflow is tailored to the specific needs of a project, allowing for customization according to the project's requirements.
_______ gadgets in JIRA Dashboards are used for tracking progress and key performance indicators (KPIs).
- Chart
- Metric
- Status
- Task
Chart gadgets in JIRA Dashboards are commonly used for tracking progress and displaying key performance indicators (KPIs) such as burndown charts, velocity charts, and pie charts. These visual representations help teams monitor their performance and make data-driven decisions.
What is the primary goal of Agile implementation?
- Enhancing customer satisfaction
- Maximizing team productivity
- Minimizing project duration
- Reducing project costs
The primary goal of Agile implementation is to enhance customer satisfaction by delivering valuable software iteratively and incrementally, adapting to change, and fostering collaboration between cross-functional teams.
A Release Burndown Chart provides insights into the progress of completing a _______.
- Feature
- Project
- Release
- Sprint
A Release Burndown Chart tracks the completion progress of a release, showing how much work is left to be done over time. It helps teams understand if they are on track to meet their release goals and allows for adjustments to be made if necessary.
In JIRA, you can use the _______ field to narrow down your search results based on issue status.
- Assignee
- Description
- Priority
- Status
In JIRA, the Status field allows users to filter search results based on the current status of issues. This is particularly useful when you want to focus on issues that are in a specific state, such as "Open," "In Progress," or "Resolved." By selecting a status from the dropdown menu, you can refine your search and find relevant issues more efficiently.
Your team is working on a highly sensitive project, and you need to ensure that only a specific group of users can view and edit certain issues within the project.
- Component Permissions
- Issue Security Schemes
- Project Permissions
- Workflow Permissions
Issue Security Schemes restrict the visibility of issues based on security levels. By configuring Issue Security Schemes, you can restrict access to specific groups or users, ensuring that only authorized individuals can view and edit sensitive issues within the project.
How can you change the assignee of an issue in JIRA?
- Edit the issue and type the new assignee's name
- Go to the issue, click on the "Assignee" field, select a new user
- Use the "Assign" button on the issue screen
- Use the "Move" operation to assign the issue to a different user
To change the assignee of an issue in JIRA, you can simply click on the "Assignee" field within the issue, which will allow you to select a new user from a dropdown menu. This action directly assigns the issue to the selected user.
In Agile, the _______ is responsible for the overall vision of the product and managing the product backlog.
- Agile Coach
- Development Team
- Product Owner
- Scrum Master
In Agile methodology, the Product Owner is responsible for defining the features of the product and deciding on the priority of work. They also manage the product backlog, ensuring it is properly groomed and ready for the team to work on. The Product Owner holds the overall vision of the product and communicates it to the development team.
What are JIRA plugins and add-ons used for in JIRA?
- Automating repetitive tasks in JIRA
- Enhancing JIRA's functionality
- Integrating JIRA with other tools and systems
- Providing additional features and capabilities
JIRA plugins and add-ons are utilized to provide additional features and capabilities beyond the core functionality of JIRA. They can extend its functionality by adding new features, integrations, or automation capabilities.
In JIRA, can you share a dashboard with users who don't have JIRA accounts?
- No, sharing is only possible with registered users.
- No, sharing is restricted to JIRA administrators only.
- Yes, by exporting the dashboard as a PDF.
- Yes, by generating a public link.
In JIRA, you can share a dashboard with users who don't have JIRA accounts by generating a public link. This allows non-registered users to view the dashboard without needing a JIRA account. It's a useful feature for sharing project progress or important information with stakeholders outside of the JIRA system. However, it's important to be cautious with sharing sensitive information and ensure that the appropriate permissions are set for the dashboard.