Project Creation (10%-15%) Flashcards
Big Shuggy wants to create a Jira project, and he has the following requirements:
- Ability to prioritize work on a daily basis using an Agile board
- Ability to work on issues in iterations but with varying duration
- Allow project administrators to clear the Agile board right-most column whenever needed.
The project should meet all these requirements right after creation without enabling additional features.
Which project type and template should Big Shuggy create?
Team-managed project with Kanban template
Let’s go through each requirement:
“Ability to prioritize work on a daily basis using an Agile board” → Both company-managed and team-managed projects have a Kanban Board.
“Ability to work on issues in iterations but with varying duration” → Working in iterations with varying duration means that the Scrum template is unsuitable. Kanban Template must be used.
“Allow project administrators to clear the Agile board right-most column whenever needed” → Only team-managed projects allow project administrators to clear the right-most column of an Agile Board manually.
In summary, the appropriate project type is “Team-managed project,” and the suitable template is “Kanban.” So Team-managed project with a Kanban template must be used.
Team-managed software projects come with three roles by default, what are they?
Administrator - Admins can do most things, like update settings and add other admins to the project. They can manage features, customize issue types, and add rules on the board. Admins require product access to Jira Software to benefit from this role.
Member - Members are a part of the team. They can create issues, edit, comment, move them into different statuses, and generally collaborate on your project’s work. Members require product access to Jira Software to benefit from this role.
Viewer - Viewers can search through and view issues in your project but not much else. You can give any registered user on your Jira site this role without extra product access.
What are 2 features unique to company-managed projects
- Custom swimlanes can be created and are based on JQL queries
- Sub-filters can be configured
Scenario:
Hannah is a scrum master and is granted all the needed permissions to view, create, delete, and edit issues on the scrum company-managed project “MLOPS”. She is also able to set due dates, comment, log work on issues as well as manage sprints. Hannah is also the Scrum board administrator.
However, Hannah is unable to rank subtasks in the backlog, why?
It is not possible to rank subtasks issue types
As stated in this open suggestion JSWCLOUD-7992, it is not yet possible to display subtasks in a scrum backlog, be it company-managed or team-managed.
Scenario:
A team in your company asked you to create a project that will meet the following requirements:
- Ability to prioritize work on a daily basis using a backlog and an Agile board
- Ability to work on issues in weekly iterations
- Ability to update workflow status names by the project administrator
The project should meet all these requirements right after creation without the need to enable additional features
Which project type and template should you create?
Team-managed project with Scrum template
Let’s go through each requirement:
“Ability to prioritize work on a daily basis using a backlog and an Agile board”: Both company-managed and team-managed projects can have a backlog and an Agile board and allow defined users to prioritize and rank issues whenever they want.
“Ability to work on issues in weekly iterations”: Working in weekly iterations means using sprints. Sprints are supported by both scrum company-managed projects and scrum team-managed projects.
“Ability to update workflow status names by the project administrator”: Only team-managed projects allow the project administrator to change the workflow status names.
Scenario:
Adam wants to create a team-managed project and is wondering which project access level he should use to meet the following requirements:
- Allow team members he is working within other Jira Kanban projects to rank issues in the new team-managed project’s backlog.
- No need to assign any project roles to team members after creating the team-managed project
Identify the project access level that Adam should use:
“Open
Let’s go through each requirement:
“Allow team members he is working within other Jira Kanban projects to rank issues in the new team-managed project’s backlog”: You can rank issues in a team-managed project if you are granted the “Work on issues” set of permissions. Besides, you need to have a Jira Software Product License. Since Adam’s team members were already working on another Jira Software project, we can assume they already have a Jira Software License.
“No need to assign any project roles to team members after creating the team-managed project”: If you don’t need/want to assign project roles to team members and also allow those team members to be able to view your issues, this means that the project access cannot be “Private.” Because if the project has “Private” access, only admins and people you add to the project can search for, view, create, or edit its issues.
Team-managed software projects have three simple access levels. What are they?
- Open
When a project is open, anyone on your Jira site can view, create, and edit issues in your project. With this access level, Jira gives anyone who logs into your Jira site the Member role in your project. - Limited
When a project is limited, anyone on your Jira site can view and comment on issues in your project. But, they can’t edit them or create new ones. With this access level, Jira gives anyone who logs into your Jira site the Viewer role in your project. - Private
When a project is private, only Jira admins and people you add to the project can see it in their project directory or its issues in search results.
Scenario:
You have just been granted access to a Jira Software Cloud site.
What should you do to be able to create team-managed projects in this one supposing that all site configuration is at its default?
Nothing
Explanation: By default, anyone can create team-managed projects. Out of the box, Jira Software gives end users the Create team-managed projects global permission. Jira admins can prevent users from creating team-managed projects by managing which groups are granted this permission.
As a project admin, you can edit 6 project details, what are they?
- Name
- URL
- Avatar
- Description
- Project lead
- Default assignee
Name two features unique to team-managed projects.
- Multiple issues can be created at once
- New issue types can be created by the project administrator
True or False - only team-managed projects allow the creation of multiple issues at once.
True
You can rank issues in a team-managed project if (Two)
- You are granted the “Work on <project> issues” set of permissions</project>
- And if you have a Jira Software Product License.
When you create a new company-managed project from a template which three schemes are unique?
- Issue Type Scheme
- Screen Scheme
- Workflow Scheme
True or False - The team-managed project does not have Issue security levels.
True
Note - Team Managed Projects do have a similar feature which is named “Restrict”
True or False - Team-managed boards do not support sub-filters.
True
