MultipleChoice
[Access, Permissions, Security]
An excerpt of the DEV permission scheme is shown:
Project Permissions|Users / Groups / Project Roles
Administer Projects | Project Role (Administrators)
View Development Tools | Project Role (Core), Project Role (Sprint Team)
Manage Sprints | Project Role (atlassian-addons-project-access), Project Role (Core)
Ahmed is a project administrator in DEV and not a Jira administrator. He is unable to create sprints in DEV. What should Ahmed do?
OptionsMultipleChoice
[Workflows and Automation]
A company-managed project uses a single workflow for two issue types: Blogs and Ideas. Youreceived several new requirements. To satisfy one of them, you must create a second workflow. Identify that requirement.
OptionsMultipleChoice
[Issue Types, Fields, Screens]
You want to use a bulk operation to move issues between two company-managed projects that use different field configurations. Which field will definitely be updated?
OptionsMultipleChoice
[General Project Configuration]
A new team requests a Jira project. They must be able to:
* Manage and prioritize all work from a central backlog.
* Track progress with a burndown chart.
* Move pre-production defects and production defects through a different QA process.
* Have the project share its schemes with another project in the future.
Which project type fulfills these requirements?
OptionsMultipleChoice
[Access, Permissions, Security]
All company-managed projects share the same permission scheme and workflow scheme. New requirements state:
* Only auditors should be able to use the 'Needs Audit' workflow transition.
* All auditors work across all the projects.
How should auditors be configured?
OptionsMultipleChoice
[Issue Types, Fields, Screens]
You are using a bulk operation to move a few stories from a company-managed project to a team-managed project. What will happen to the stories?
Options