Changing the Standard Working Days affects the Burndown Chart, as this chart relies on working days

to plot the ideal and actual burn of work during a sprint. Adjusting working days ensures the

burndown chart accurately reflects the team's actual schedule.

Versions: Versions (also known as releases) allow you to group issues by project phases, assign fixed

start and end dates, and track progress.

Sprint: Sprints also have defined start and end dates, and unresolved issues can be automatically

carried over to the next sprint, aligning with the requirement to move work between phases.

priority changed to High before now(): This returns issues where the priority was set to High at any

point in the past, regardless of its current value.

priority was High: This returns issues that had High priority at some point, whether or not they still

have it. Both satisfy the requirement to show issues where the priority was High in the past and may

or may not still be.

The Labels field type allows users to select multiple values and add new ones on the fly if they don't

already exist. This meets the team's need to flag issues with one or more colors and dynamically add

new color options.

When multiple components are selected on issue creation, Jira cannot determine a single default

assignee if each component has a different assignee rule. In this case:

● Hardware → Component lead (Vincent Choy)

● Software → Project default (Alana Grant)

● Infrastructure → Unassigned

Since the assignee logic conflicts, Jira defaults to Unassigned to avoid ambiguity.

Versions in a company-managed project are designed to represent project phases with fixed start and

end dates, allow tracking of resolved and unresolved issues, and automatically move unresolved

issues to the next version. They also support reporting by version, making them the best fit for this

use case.

Link issue: Allows users to link to another Jira issue, providing contextual connections between

related work items.

Link Confluence page: Enables linking a Confluence knowledgebase article directly to the Jira issue.

Add web link: Lets users attach external URLs, such as industry white papers, to the issue for easy

reference.

If Marcella can see TIS issues but not the TIS project board, it's likely because the board filter is not

shared with her. Boards in Jira are based on filters, and if the filter isn’t shared with a user, the board

won’t be visible to them - even if they have access to the project and issues.

The Average Age Chart shows the average age of unresolved issues over time. It helps visualize how

long, on average, issues have been open on any given day, which directly reflects how unresolved

issues are trending.

The Schedule Issues permission is required to edit date-related fields, such as the Due Date and Fix

Versions. Since the rule edits the Fix versions field and responds to Due Date changes, lacking this

permission will cause the rule to fail.