What should you consider when designing a workflow for compliance or regulatory requirements?
- Adding strict conditions to restrict access to sensitive information
- Ensuring that each workflow transition is manually approved by a manager
- Including a detailed audit log of all workflow actions
- Incorporating necessary approvals, reviews, and documentation steps
When designing a workflow for compliance or regulatory requirements, it's essential to consider incorporating necessary approvals, reviews, and documentation steps. This ensures that all necessary checks and balances are in place to comply with regulatory standards and mitigate risks associated with non-compliance.
The project administrator can control who can transition issues by configuring _______.
- Boards
- Fields
- Sprints
- Workflow
By configuring workflows in JIRA, project administrators can define the transitions between different statuses of an issue. They can control which users or groups have permission to execute these transitions, thereby managing who can move issues through the workflow stages.
Scenario: A colleague wants to receive a daily email notification with a list of all newly created issues assigned to them. How can they set up this notification in JIRA?
- JIRA Add-ons
- JIRA Automation
- JIRA Notification Schemes
- JIRA Workflow Triggers
JIRA Automation can be configured to send automated email notifications based on specified triggers, such as newly created issues assigned to a particular user. This feature fulfills the requirement efficiently.
Can issues from one JIRA project be linked to issues in another project? If so, how?
- No, issues can only be linked within the same project
- Yes, by assigning the same issue key to both projects
- Yes, by copying the issue to another project
- Yes, using issue linking functionality
Issues from one JIRA project can indeed be linked to issues in another project using the issue linking functionality. This feature enables users to establish relationships between related issues across different projects, facilitating cross-project collaboration and tracking dependencies.
You are setting up permissions for a JIRA Service Desk project, and you want customers to be able to create issues but not see all the details of existing issues.
- Customer Permissions
- Customer Portal Permissions
- Issue Security Schemes
- Service Desk Permissions
Customer Portal Permissions control what customers can see and do in the customer portal, including their ability to view existing issues. By configuring these permissions, you can restrict customers from viewing all the details of existing issues while still allowing them to create new ones.
Post-functions in workflows are used to perform _______ actions after an issue transitions to a new status.
- Automated
- Custom
- Manual
- Pre-defined
Post-functions automate actions that occur after an issue transitions, streamlining processes and ensuring consistency. They can be predefined or custom-built based on specific workflow requirements.
In JIRA, _______ is a key area where system administrators need to ensure proper configuration and monitoring.
- Audit Logs
- Issue Types
- System Dashboard
- User Permissions
The system dashboard provides an overview of JIRA's performance and key metrics, helping administrators monitor and manage the system effectively.
In a Scrum board, what is the purpose of the "backlog"?
- A board for tracking team member availability
- A list of features or tasks to be completed
- A repository for completed tasks
- A section for tracking bugs and issues
The backlog in a Scrum board serves as a prioritized list of features, user stories, or tasks that need to be completed during the project. It represents the product backlog and is constantly refined and updated based on feedback and changing requirements.
In JIRA, can an issue be assigned to multiple assignees simultaneously?
- Depends on the permission scheme
- Depends on the project configuration
- No
- Yes
In JIRA, an issue can only be assigned to one assignee at a time. Assigning to multiple assignees is not a built-in feature. Each issue can have only one assignee responsible for it. This helps maintain accountability and clarity regarding who is responsible for resolving the issue.
Which JIRA issue type is typically used to represent user requirements?
- Bug
- Epic
- Story
- Task
In JIRA, the "Story" issue type is typically used to represent user requirements or user stories. User stories describe specific functionality or features from an end user's perspective and are commonly used in agile development methodologies.