Recap - Are you smarter than a Jira Admin? | August 2024
Welcome to September everyone! In many places this begins the changing of the seasons, but before we welcome Fall, let’s remember the end of Summer in style.
Our second #AYSTACA saw 90+ folks compete for fabulous prizes (listed below), but more importantly, offered a chance for the community to get together and have some fun while learning about Jira with @Robert Wen and @Robert Hean
Congratulation to our Leaderboard:
HansP 🥇
Amanda Barber🥈
Dhruvil Shah🥉
The Jira Guy🏆
Chris Rogers🏆
Magdalena Zhisheva🏆
Michel Neeser🏆
Brandon Davies🏆
Tommy🏆
Shane Garnett🏆
Podium Prizes:
1st place - $100 Atlassian Community Gift Card
2nd place - $50 Atlassian Community Gift Card
3rd place - $25 Atlassian Community Gift Card
Top 10:
100% Free certification vouchers from Atlassian University
Special digital badge + name in honor roll on online community
If you are on the leaderboard, please comment from your "real" profile or link the same in the comment so that we can get you this awesome badge and your 100% free certification vouchers.
Top 3, post you have confirmed your account, and we will reach out to you for your gift cards as well.
Also, Please DM Sajit Nair if you don't get your prizes by end of next week.
Don't forget to sign up for the next episode of #AYSTA which is #3 - AYSTACA - on September 20th, 2024.
If you missed the live broadcast, check out the recording here.
To assist you with your test prep, here are the questions and answers from this session for your studying pleasure!
Q1: What is a Jira issue?
A) A type of bug report
B) A project management tool
C) A task or work item within a project
D) A user complaint
Correct Answer: C
Reasoning
A) Incorrect: While Jira issues can include bugs, they aren't limited to them.
B) Incorrect: Jira itself is the project management tool, not the issue.
C) Correct: A Jira issue represents a task, work item within a project. Examples include bugs, stories, tasks, issues and more.
D) Incorrect: A user complaint could be tracked as an issue, but it is not a jira issue.
Q2: Which of the following best describes an Epic in Jira?
A) A large user story that can be broken down into smaller tasks
B) A critical bug that needs immediate attention
C) A document repository
D) A report on team performance
Correct Answer: A
Reasoning
A) Correct: An Epic represents a big piece of work that can be split into smaller stories or tasks.
B) Incorrect: Bugs are usually tracked as a specific issue, not an Epic.
C) Incorrect: While documents can be attached to Epics, Jira does not use Epics for document storage.
D) Incorrect: Epics can appear in reporting, however, Epics do not function as reports.
Q3: What does the 'Watch' feature in Jira allow you to do?
A) Assign the issue to yourself
B) Receive notifications when the issue is updated
C) Track the time spent on an issue
D) Close the issue
Correct Answer: B
Reasoning
A) Incorrect: 'Watch' does not change issue assignment.
B) Correct: 'Watch' allows users to follow an issue and receive updates on any changes.
C) Incorrect: Time tracking is a different feature.
D) Incorrect: Watching does not give permission to close the issue.
Q4: Which task can a Jira Cloud administrator perform?
A) grant Jira admin privileges to another user
B) grant org admin privileges to another user
C) add another Jira admin to a project role
D) add another Jira admin to a group
Correct Answer: C
Reasoning
A. Incorrect. Only org admins can grant or remove product access, including Product Admin.
B. Incorrect. Only org admins can grant org admin privileges.
C. Correct. Jira admins can add anyone to project roles, including other Jira admins.
D. Incorrect. Only org admins can manage groups.
Q5: What could be impacted when you rename an issue type?
A) custom field contexts
B) saved filters
C) issue type schemes
D) workflow schemes
Correct Answer: B
Reasoning
A. Incorrect. Custom field contexts are based on the project and issue type, so renaming an issue type does not affect the context's functionality or association. The context will still apply as before, though the visible name of the issue type will change.
B. Correct. Saved filters that reference the issue type by name in JQL queries will break if the issue type name changes. Users will need to update these filters to reflect the new issue type name to ensure they continue to return the correct results.
C. Incorrect. Issue type schemes associate projects with issue types based on their IDs, not their names. Renaming an issue type does not impact the scheme configuration itself, though the new name will be displayed.
D. Incorrect. Workflow schemes link workflows to issue types by ID, so renaming an issue type does not affect the underlying association. The workflows will continue to function as expected for the renamed issue type.
Q6: What can NOT be migrated from one Jira Cloud site to another?
A) automation rules
B) custom fields
C) attachments
D) deleted issues
Correct Answer: D
Reasoning
A. Incorrect. Automation rules are imported.
B. Incorrect. Custom fields are imported.
C. Incorrect. Attachments can be imported.
D. Correct. Once issues are deleted in Jira, they are permanently removed and cannot be recovered or migrated. Deleted issues do not exist in the system to be included in any migration process.
Q7: What must you do so users can log Time Spent in a company-managed project?
A) Grant them a global permission.
B) Grant them a project permission.
C) Enable Time tracking in system settings.
D) Add the Time tracking fields to workflow.
Correct Answer: B
Reasoning
A. Incorrect. Logging time is controlled via project permission, not global permissions. Global permissions relate to actions affecting the entire Jira instance, while time logging is project-specific.
B. Correct. Users need the ""Work On Issues"" project permission to log time on issues. This permission allows them to record time spent on individual issues within the project.
C. Incorrect. Time tracking is already always enabled in Jira Cloud.
D. Incorrect. Time tracking fields are not tied to specific workflow transitions or steps, but rather exist independently for issues. The fields for logging time are standard and do not require workflow configuration to be used.
Q8: Sandy wants to move one of her assigned issues from the backlog into a planned sprint.
Which permission does she need?
A) Manage sprints
B) Move issues
C) Assignable User
D) Edit Issues
Correct Answer: D
Reasoning
A. Incorrect. The “Manage sprints” permission is used to create, start, complete, and reopen sprints.
B. Incorrect. She needs to rank issues, not move them.
C. Incorrect. She doesn't need the “Assignable User” permission to rank issues. And she already has it since she has assigned issues.
D. Correct. To rank issues, users need “Edit Issues” and “Schedule Issues” permissions, as well as the “Browse Projects” permission.
Q9: Ravi is only able to transition some of the issues displayed in a saved filter via a bulk operation.
Identify the root cause.
A) post-functions and triggers
B) conditions and permissions
C) columns and statuses
D) security levels and roles
Correct Answer: B
Reasoning
A. Incorrect. Neither workflow triggers nor post-functions would prevent transitioning through the workflow.
B. Correct. Workflow conditions (that use permissions) may prevent him from transitioning issues. Also, the issues may be in different projects and he may be missing Transition Issues permission in the other project(s).
C. Incorrect. Statuses might be correct if they are protected by step properties but columns are irrelevant when doing a bulk transition.
D. Incorrect. Roles might be correct if workflow conditions use roles, but security levels are irrelevant because he sees the issues.
Q10: You need to ensure that every issue created in a project always has an assignee.
Which default assignee definitely meets the requirement?
A) Component Lead
B) Project Lead
C) Component Default assignee
D) Project Default Assignee
Correct Answer: B
Reasoning
A. Incorrect. If no component lead is selected for a component, the issue will stay unassigned.
B. Correct. It's mandatory to pick a project lead, so this setting will make sure that each issue is assigned to a user.
C. Incorrect. Component Default assignee can be Unassigned or Project Default, which could be Unassigned. So it's possible that issues would stay unassigned.
D. Incorrect. You can set the project Default Assignee to Unassigned, so issues would stay unassigned.
Q11: Which project setting can be updated by either a Jira admin or a project admin?
A) project key
B) project type
C) project category
D) project name
Correct Answer: D
Reasoning
A. Incorrect. Only Jira admins can update the project key.
B. Incorrect. No one can actually change the project type from the Project Details page; neither a project admin nor a Jira admin. You need to create a new project of a different type and move all of the existing issues into it using a bulk operation.
C. Incorrect. To edit the project category, you must be a Jira admin.
D. Correct. Project admins or Jira admins can modify the project name.
Q12: You want to disable sub-tasks globally in Jira.
What must you do beforehand?
A) Remove sub-tasks from all issue type schemes.
B) Resolve all unresolved sub-tasks.
C) Rename the sub-task issue type.
D) Convert all sub-tasks to standard issue types.
Correct Answer: D
Reasoning
A. Incorrect. You don't have to update issue type schemes.
B. Incorrect. Sub-tasks must be converted to standard issue types but they don't necessarily need to be resolved.
C. Incorrect. Sub-tasks must be converted to standard issue types regardless of their name.
D. Correct. You can't disable sub-tasks if one or more sub-tasks have already been created. You must convert these sub-tasks to standard issue types before disabling.
Q13: Which issue type automatically inherits its security level from its parent without the use of automation?
A) story
B) task
C) bug
D) sub-task
Correct Answer: D
Reasoning
A. Incorrect. Standard issue types do not automatically inherit the security level of their parent epics without the use of automation.
B. Incorrect. Same as above.
C. Incorrect. Same as above.
D. Correct. Sub-tasks automatically inherit the security level from their parent issue, as they are designed to be dependent on or related to their parent.
Q14: Which Jira configurations do NOT ever impact notifications?
A) gadgets
B) security levels
C) permission schemes
D) custom events
Correct Answer: A
Reasoning
A. Correct. Gadgets are not related to notifications.
B. Incorrect. If users cannot see issues – due to security levels – they will not be notified about them. So security levels impact notifications.
C. Incorrect. If users cannot see issues – due to missing Browse Projects permission – they will not be notified about them. So permission schemes impact notifications.
D. Incorrect. Workflow post-functions can fire custom events that are configured in notification schemes.
Q15: You received requirements for both a team-managed and a company-managed project.
Which requirement can be satisfied only with a company-managed project?
A) restrict who can transition issues
B) connect the project to Bitbucket
C) display sub-tasks on the board
D) add a custom notification event
Correct Answer: D
Reasoning
A. Incorrect. Both projects can restrict who can use a particular transition. In company-managd projects, it is done via a condition. In team-managed projects, it is via a workflow rule.
B. Incorrect. Both types of projects can connect to Bitbucket.
C. Incorrect. Both projects can display sub-tasks on the board.
D. Correct. Custom notification events can only be added to company-managed projects.
Q16: Rufus is not able to log time on a bug in a team-managed project.
Identify a possible reason why.
A) He lacks “Work On Issues” project permission.
B) Time tracking is disabled in Jira.
C) The Time tracking field is missing on the issue type.
D) He already logged work on this issue.
Correct Answer: C
Reasoning
A. Incorrect. The “Work On Issues” project permission exists in company-managed projects, not team-managed projects.
B. Incorrect. Time tracking is always enabled in Jira Cloud projects.
C. Correct. The Time Tracking field must be present on the Bug issue type.
D. Incorrect. Assuming the Time Tracking field is present, he can log Time Spent multiple times on the same issue.
Q17: You just archived version 1.0 in a particular Jira project.
Which statement is true?
A) 1.0 is removed from the Release Hub.
B) 1.0 can be unarchived in the project.
C) Unresolved 1.0 issues are automatically closed.
D) Unresolved 1.0 issues are automatically moved to another version.
Correct Answer:
Reasoning
A. Incorrect. The archived version remains visible in the Release Hub.
B. Correct. Archived releases can be unarchived.
C. Incorrect. Issues are not automatically closed during the process of archiving a version.
D. Incorrect. Issues are not automatically moved to another version while archiving.
7 comments
