Scenario: Your team is using JIRA to manage a software development project. You have received a request from a product owner to create a new issue type specifically for tracking security-related tasks. What type of issue should you create, and why?
- Bug: This issue type is used to track defects or issues in the software.
- Epic: This issue type allows for tracking large bodies of work that can be broken down into smaller tasks.
- Story: This issue type is suitable for tracking user stories or requirements.
- Task: This issue type is ideal for tracking small, actionable items.
In this scenario, the most appropriate issue type to create for tracking security-related tasks is a "Bug." Security-related tasks often involve identifying and addressing vulnerabilities or issues in the software, which aligns with the purpose of the Bug issue type. Bugs are used to track defects or issues in the software, making them suitable for recording and addressing security concerns.
Loading...
Related Quiz
- What is the purpose of the JIRA Backup and Restore feature?
- What is the difference between a "Shared Configuration" and a "Project-specific Configuration" in JIRA?
- How can you grant specific permissions to a group of users for a project?
- You are an experienced JIRA administrator, and a new version of a critical JIRA plugin is released. What steps should you take before upgrading the plugin to ensure a smooth transition?
- In JIRA, what is a common practice when naming tasks or sub-tasks?