Versions Compared

Old Version 19

changes.mady.by.user Caelor Marketplace Support

Saved on

compared with

New Version Current

changes.mady.by.user Kresimir Nikolic

Saved on

Key

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

The Moscow method is a prioritization technique used in management, business analysis, and software development to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement.

Info

MoSCoW is available as a custom field type. Values and colours defined in the app configuration screen are default values and used if there are no other configuration scheme contexts created.

MoSCoW categories:

StatuscolourGreentitleMUST
Image Added
Macrosuite divider macro
dividerWidth100
dividerTypeonly_divider
emoji{"id":"smile","name":"Smiling Face with Open Mouth and Smiling Eyes","short_names":["smile"],"colons":":smile:","emoticons":["C:","c:",":D",":-D"],"unified":"1f604","skin":null,"native":"😄"}
textColor#000000
dividerWeight3
labelPositionmiddle
textAlignmentcenter
iconColor#0052CC
fontSizemedium
textDivider text
emojiEnabledfalse
dividerColor#DFE1E6
dividerIconbootstrap/CloudsFill

MoSCoW categories:

Image Added

The vital things for the product. If even one requirement is not included in the product delivery, it should be considered a failure.

Status
colourBlue
titleSHOULD

Image Added

Requirements are also critical but not necessary for delivery in the current time box. Product will work works without should feature, but those still have crucial business value.

Status
colourYellow
titleCOULD

Image Added

Requirements are not critical and ofter often considered as nice to have. It is possible to reevaluate those requirements after some time. StatuscolourRedtitleWon't

Image Added

Requirements have the lowest priority. This is because we are not deleting them from the backlog but usually sort them on the bottom.

Macrosuite divider macro
dividerWidth100
dividerTypeonly_divider
emoji{"id":"smile","name":"Smiling Face with Open Mouth and Smiling Eyes","short_names":["smile"],"colons":":smile:","emoticons":["C:","c:",":D",":-D"],"unified":"1f604","skin":null,"native":"😄"}
textColor#000000
dividerWeight3
labelPositionmiddle
textAlignmentcenter
iconColor#0052CC
fontSizemedium
textDivider text
emojiEnabledfalse
dividerColor#DFE1E6
dividerIconbootstrap/CloudsFill

Create and configure the custom field

Note

To create and configure the MoSCoW priorization prioritization custom field, you must be logged in as a user with Jira Administrator permissions.

Macrosuite divider macro
dividerWidth100
dividerTypeonly_divider
emoji{"id":"smile","name":"Smiling Face with Open Mouth and Smiling Eyes","short_names":["smile"],"colons":":smile:","emoticons":["C:","c:",":D",":-D"],"unified":"1f604","skin":null,"native":"😄"}
textColor#000000
dividerWeight3
labelPositionmiddle
textAlignmentcenter
iconColor#0052CC
fontSizemedium
textDivider text
emojiEnabledfalse
dividerColor#DFE1E6
dividerIconbootstrap/CloudsFill
Image Added

Macrosuite divider macro
dividerWidth100
dividerTypeonly_divider
emoji{"id":"smile","name":"Smiling Face with Open Mouth and Smiling Eyes","short_names":["smile"],"colons":":smile:","emoticons":["C:","c:",":D",":-D"],"unified":"1f604","skin":null,"native":"😄"}
textColor#000000
dividerWeight3
labelPositionmiddle
textAlignmentcenter
iconColor#0052CC
fontSizemedium
textDivider text
emojiEnabledfalse
dividerColor#DFE1E6
dividerIconbootstrap/CloudsFill

  1. Go to Settings Apps → Issues Manage your apps → Custom FieldsField Suite

  2. Click on Create a new custom field of type CFS - MoSCoW PriorizationAdd name and descriptionbutton on the right side of the screen.

  3. Select MoSCoW Prioritization and click Next.

  4. Name and add a description to your field then click Next.

  5. Select between two available View options and click Next.

  6. Associate the field to the appropriate screens and click Create. You must associate a field to a screen before it will be displayed.

  7. Click on 1 Context and click Create, edit or delete contexts on the dialogue.

  8. Click Edit custom field config.

  9. Set new names and colors for MoSCoW fields.

Note

Steps 5, 6 and 7 are not required. You can use the default values that are set in the app configuration screen.

Image Removed

MoSCoW Priorization

That’s it! You can now navigate to your issue and enhance it with MoSCoW Prioritization.

Image Added

MoSCoW Prioritization JQL queries

CFS - MoSCoW prioritization can be used in JQL. It allows you to search for issues that include custom field values. To find issues that include multilevel select picker values enter the "CustomField_Name". Below are a few useful examples.

"CFS - MoSCoW PriorizationPrioritization" = must

Search for all issues that contain must priority.

"CFS - MoSCoW PriorizationPrioritization" != must

Search for all issues that don´t contain must priority.

"CFS - MoSCoW PriorizationPrioritization" is EMPTY

Search for all issues where the custom field is empty.

"CFS - MoSCoW PriorizationPrioritization" is not EMPTY

Search for all issues where the custom field is not empty.

Macrosuite divider macro
dividerWidth100
dividerTypeonly_divider
emoji{"id":"smile","name":"Smiling Face with Open Mouth and Smiling Eyes","short_names":["smile"],"colons":":smile:","emoticons":["C:","c:",":D",":-D"],"unified":"1f604","skin":null,"native":"😄"}
textColor#000000
dividerWeight3
labelPositionmiddle
textAlignmentcenter
iconColor#0052CC
fontSizemedium
textDivider text
emojiEnabledfalse
dividerColor#DFE1E6
dividerIconbootstrap/CloudsFill

Use cases

Cp content card macro
data{"type":"page","variant":"grid","columns":1,"contributors":[],"labels":[],"spaces":[],"pagination":"infinite","sorting":"created","ordering":"ascending","limit":8,"enrichment":"manually","manuallyPicked":[{"id":"a0e7c75d-d08a-483d-90c3-c42674680682","position":0,"contentId":"625475626"}],"_migrations":["migrateContentCards"]}