NN Issue Tracker

Wiki
,
1

Why is it important?

If the NN Issue tracker is not set up properly then the “Issue tracker skipped” message appears in Architect. It means that the revision data is visible only on the component level, no proper linking is set between PIs, WIs, SRs, release notes. It leads to difficulties with composing, QA, etc.

Flow

Open the Architect > click on the Novulo button > click on the Architect options:

image
image555×645 23.1 KB

Check personal settings: Issue tracker username and password must be set.

image

Scroll Issue tracker url and click on the Test button. The popup with the success message must be seen.

image

Open a needed app > Click on the Novulo button > click on the “Save as component” option > The window with the PIs must be visible > choose a PI.

image
image489×506 7.81 KB

The window “Revision information” must be visible. Fill in the valid data. The main fields are:

image
image688×797 26.4 KB

  • New issue (1) > if you need to create a PI;
  • Main issue (2) > will be automatically set if the chosen PI has the main PI;
  • Only for a newly created PI: Issue type (feature, documentation, bug, restructuring, UX, performance, epic, story) and Issue description;
  • Issue routing (3),
  • Work item message (4) > revision description;
  • Message type > your revision description will be published with the chosen message type (notion, design, test, etc.);
  • Next routing line (5) > test, develop, etc.;
  • Issue resolution(6) = always Open;
  • Use hour registration checkbox (7), Start time (8), End time (9),
  • Revision status (10).

Best practice

WI message must be descriptive but short: describe in a few words what was be done on component (new property is added, plugin is updated, etc.). It could help while writing release notes.

1 Like