[TSC] How do we attach an Requirement to a Feature?

[felixpou]

Do we create a Feature issue type?
How do we attach an Requirement to a Feature? (could be just an hyperlink in the description but if there is a way to add a specific that could enable future automation.)

[felixpou]

@peterbrightwell could you give a look at this?

[peterbrightwell]

I've looked at this and tried it out some of it in my personal repos and suggest the following for new features (I didn't try the parts in italics yet, but Copilot has suggestions)

• Create .github/ISSUE_TEMPLATE/feature_request.yml (or whatever) that specifies a required attribute "requirement_link".
• Create .github/ISSUE_TEMPLATE/config.yml that disables blank issue creation so forcing the attribute to be provided
• The link can be a full URL or short-form dmf-mxl/mxl-requirements#<num>
  - Run a GitHub Action that runs on a new issue to check the URL is valid
• The issue description will then show a clickable requirement link
  - Perhaps some GitHub CLI scripting can be used to update existing issues
• Add a new custom field "linked-requirement" on the Kanban
• Add this to the Kanban view (perhaps create a Feature view?)
  - Update the GitHub Action to populate that from the issue description

I can show some of this on the TSC call later today

[felixpou]

worth a try. And this "ISSUE_TEMPLATE" would be associate with additional issue type "Feature"

[peterbrightwell]

Yes that's right. This only would apply to Feature issue types and we should probably have a separate template for bug fix issues.
Quick demo and discussion on today's TSC (2025-10-16) -- we should try it.

[peterbrightwell]

I've been experimenting on my fork, and it looks like we need to move the SPDX comment lines to the end of the templates otherwise the templates are not recognised by GitHub. Note that we already have several templates that should be appearing in a menu when we select "New issue".

[peterbrightwell]

This is now merged in #195. When someone clicks on Create new issue they have to choose from five options. In this case use "Feature" (not "Feature request" which is about new ideas (maybe we should rename that "Idea"?)

[felixpou]

This may be good enough for now. If this link to the requirement would be in a custom field instead, this would help quickly verify that a Feature has a requirement and to find it. For example I have tried this in here: MXL TSC Board (view)