Versions Compared

Old Version 2

changes.mady.by.user Frank Lapa

Saved on

compared with

New Version Current

changes.mady.by.user Frank Lapa

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Index

  • General concepts

    • What is a project scheme?

    • What is

...

    • Jira

...

    • field?

    • What is

...

What is a dashboard?

...

Board configurations

  • Given a scenario, recommend an appropriate board type

  • Configure boards across multiple teams and projects

  • Configure board columns to match a workflow process

  • board filters, sub-filters, and quick filters

  • Estimation and time tracking on Scrum boards

  • Swimlanes, card colors, card layout, working days, and issue detail view

...

Troubleshoot board and filter configurations

...

    • Jira custom field?

    • Jira Screens, field Layouts, cards

  • Managing projects

    • Project permissions

    • Project roles

    • Versioning and manage releases

    • Sub-categorize issues

    • Component and auto assignment

    • Issue field Layouts

    • Enrich issues

1. General concepts

1.1 What is a project scheme?

A project scheme in Jira is like a set of rules and tools that determine how a particular project operates

Drawio
mVer2
zoom1
simple0
inComment0
custContentId162005312
pageId161611777
lbox1
diagramDisplayNameUntitled Diagram-1699019308224.drawio
contentVer2
revision2
baseUrlhttps://wiqu.atlassian.net/wiki
diagramNameUntitled Diagram-1699019308224.drawio
pCenter0
width1259
links
tbstyle
height621.5
Drawio
mVer2
zoom1
simple0
inComment0
custContentId

...

162005358
pageId

...

161611777
lbox1
diagramDisplayNameacp-620-

...

da3-slide-

...

2.drawio
contentVer1
revision1
baseUrlhttps://wiqu.atlassian.net/wiki
diagramNameacp-620-da3-

...

slide-

...

2.drawio
pCenter0
width

...

1258.9999999999998
links
tbstyle
height621.

...

409090909091
Drawio
mVer2
zoom1
simple0
inComment0
custContentId

...

162038129
pageId

...

161611777
lbox1
diagramDisplayNameacp-620-

...

day3-slide-

...

3.drawio
contentVer

...

1
revision

...

1
baseUrlhttps://wiqu.atlassian.net/wiki
diagramNameacp-620-day3-

...

slide-

...

3.drawio
pCenter0
width

...

What is a board?

1196.0500000000002
links
tbstyle
height

...

621.5
Drawio
mVer2
zoom1
simple0
inComment0
custContentId

...

161907145
pageId

...

161611777
lbox1
diagramDisplayNameacp-620-

...

day3-

...

slide4.drawio
contentVer1
revision1
baseUrlhttps://wiqu.atlassian.net/wiki
diagramNameacp-620-

...

day3-

...

slide4.drawio
pCenter0
width

...

1219.5
links
tbstyle
height

...

What is a dashboard?

621.5
Drawio
mVer2
zoom1
simple0
inComment0
custContentId

...

162103664
pageId

...

161611777
lbox1
diagramDisplayName

...

Untitled Diagram-1699019226545.drawio
contentVer2
revision2
baseUrlhttps://wiqu.atlassian.net/wiki
diagramName

...

Untitled Diagram-1699019226545.drawio
pCenter0
width

...

1259
links
tbstyle
height621.

...

5

1.2 What is

...

Jira field?

Imagine you're in a library filled with books (or "issues" in Jira). Instead of searching each shelf manually, you use JQL to tell the librarian (Jira) exactly what you're looking for, and she brings it to you. It's like using precise phrases to search for specific books!

  1. Issues: These are like the "books" in our library analogy. In Jira, an issue can be a task, bug, story, or any work item.

  2. Fields: Characteristics of an issue, like the title, author, or published date in books. In Jira, fields can be summary, assignee or created date,… etc.

  3. Operators: These help you specify your search. Think of them as the words you use to describe how you want to filter the books, like "is," "is not," "in," "before," etc.

  4. Values: The actual details you're looking for. If fields are like the characteristic "author," values would be "J.K. Rowling" or "Mark Twain."

JQL Examples

All tasks Jay has been working

Code Block
assignee = Jay

All tasks Jay is working and still not completed

Code Block
assignee = Jay AND resolution is Empty

All tasks Jay is working and still not completed or Frank is working and still not completed

Code Block
assignee = Jay AND resolution is Empty or assignee = Frank AND resolution is Empty

All tasks Jay and Frank are working and still not completed

Code Block
( assignee = Jay or assignee = Frank ) and resolution is Empty

Board configurations

Given a scenario, recommend an appropriate board type

Scenario 1

A software development team is launching a new mobile application. They plan to work in time-boxed intervals, addressing a prioritized list of features and bugs. They need to commit to specific tasks for each interval and review their progress at the end.

Answer: Scrum Board

A software development team working on a new project often operates in sprints or time-boxed intervals. The Scrum methodology is designed to address prioritized tasks within these intervals. A Scrum board is thus perfect for this setup, allowing the team to plan their sprint by selecting tasks from the backlog, tracking their progress during the sprint, and then reviewing and reflecting at the end of the sprint. It provides structure to iterative development and helps ensure that tasks are completed within the set timeframe.

Scenario 2

The customer support team handles incoming issues and queries from users. The team wants to visualize their workflow, manage the constant flow of tasks, and ensure that no ticket remains unaddressed for too long.

Answer: Kanban Board

Justification: For teams like customer support, work arrives unpredictably and doesn't fit neatly into time-boxed intervals. Instead, the emphasis is on fluidity and ensuring a steady flow of work. A Kanban board offers a visual representation of this workflow, enabling team members to pick tasks based on priority and availability. It's ideal for managing ongoing and variable tasks by visually identifying bottlenecks and ensuring consistent delivery.

Scenario 3

A product management team is collecting ideas and feedback for product enhancements. They want a space to store and prioritize these ideas (backlog) while also having a flow to address and implement the top priorities, transitioning them through different stages until completion.

Answer: Kanban with Backlog:

Justification: The product management team's work involves both collecting ideas (which may not be immediately actionable) and transitioning prioritized ideas through various stages. A Kanban board with a backlog allows the team to maintain a repository of ideas and feedback while also actioning top priorities. The backlog offers a space for ideas to be stored, discussed, and prioritized, while the Kanban board visualizes the progression of these ideas from conception to completion.

Practica examples

  • Configure boards across multiple teams and projects

  • Configure board columns to match a workflow process

  • Board filters, sub-filters, and quick filters

  • Estimation and time tracking on Scrum boards

  • Swimlanes, card colors, card layout, working days, and issue detail view

...

Attributes of a Ticket, cane be used for search them and filter them

Drawio
mVer2
zoom1
simple0
inComment0
custContentId162267297
pageId161611777
lbox1
diagramDisplayNameacp-620-day-3-slide5.drawio
contentVer1
revision1
baseUrlhttps://wiqu.atlassian.net/wiki
diagramNameacp-620-day-3-slide5.drawio
pCenter0
width1004
links
tbstyle
height680

1.3 What is Jira custom field?

More advanced fields we can create custom for a project

Drawio
mVer2
zoom1
simple0
inComment0
custContentId162005578
pageId161611777
lbox1
diagramDisplayNameacp-620-day3-slide6.drawio
contentVer2
revision2
baseUrlhttps://wiqu.atlassian.net/wiki
diagramNameacp-620-day3-slide6.drawio
pCenter0
width951
links
tbstyle
height481

1.4 Screens vs Field Layouts vs Issue cards

Drawio
mVer2
zoom1
simple0
inComment0
custContentId162234687
pageId161611777
lbox1
diagramDisplayNameacp-620-day3-slide7.drawio
contentVer3
revision3
baseUrlhttps://wiqu.atlassian.net/wiki
diagramNameacp-620-day3-slide7.drawio
pCenter0
width971
links
tbstyle
height616

Drawio
mVer2
zoom1
simple0
inComment0
custContentId162267550
pageId161611777
lbox1
diagramDisplayNameacp-620-day3-slide8.drawio
contentVer1
revision1
baseUrlhttps://wiqu.atlassian.net/wiki
diagramNameacp-620-day3-slide8.drawio
pCenter0
width1044.0000000000002
links
tbstyle
height445

...

2. Managing projects

2.1 Project permissions

Determine appropriate permissions for project team members (project, global)

2.2 Project roles

Assign team members to project roles

2.3 Versioning and manage releases

Implement versioning, manage releases, predict the impact of scope changes

2.4 Sub-categorize issues

Recommend a method to sub-categorize issues (components, labels, custom fields)

2.5 Component and auto assignment

Configure and troubleshoot automatic issue assignment (project default, components)

2.6 Issue field Layouts

Configure issue field layout

2.7 Enrich issues

Evaluate ways to enrich issues (attachments, links, time tracking, developer information)

3. Additional material

Child pages (Children Display)