@@ -294,7 +294,8 @@ Issue priority labels
294294============= ===============================================================
295295Labels ``priority:{high|medium|low} ``
296296Applicable to Issues only
297- Description To classify the impact and importance of a bug or feature
297+ Description To classify the impact and importance of a bug or
298+ :ref: `feature <feature-tracking >`
298299============= ===============================================================
299300
300301Note: Issue priorities are generally set or changed during the bug-triage or TSC
@@ -347,15 +348,18 @@ Issue only labels
347348``Regression `` Something, which was working, but does not anymore
348349 (bug subtype)
349350``Question `` This issue is a question to the Zephyr developers
350- ``Enhancement `` Changes/Updates/Additions to existing features
351- ``Feature request `` A request for a new feature
352- ``Feature `` A planned feature with a milestone
351+ ``Enhancement `` Changes/Updates/Additions to existing
352+ :ref: `features <feature-tracking >`
353+ ``Feature request `` A request for a new :ref: `feature <feature-tracking >`
354+ ``Feature `` A :ref: `planned feature<feature-tracking> ` with a milestone
353355``Duplicate `` This issue is a duplicate of another issue
354356 (please specify)
355357``Good first issue `` Good for a first time contributor to take
356358``Release Notes `` Issues that need to be mentioned in release notes as known
357359 issues with additional information
358360==================== ===========================================================
359361
360- Any issue must be clasified and labeled as either ``Bug ``, ``Question ``,
361- ``Enhancement ``, ``Feature ``, or ``Feature Request ``.
362+ Any issue must be classified and labeled as either ``Bug ``, ``Question ``,
363+ ``Enhancement ``, ``Feature ``, or ``Feature Request ``. More information on how
364+ feature requests are handled and become features can be found in
365+ :ref: `Feature Tracking<feature-tracking> `.
0 commit comments