Add an issues page field to the base application
Metadata
Current evaluation
Open, untriaged request to add a mandatory issue-reporting URL to AppMetadata; the current code exposes docs_url but has no issues_page field.
Suggested action: needs triage
Reason: AppMetadata currently has no issues_page field, and repository history shows no implementing commit, so the request remains valid. It is clearly motivated by the discussion on PR #701, but the issue has no labels or comments and leaves the exact field contract and error-message integration ambiguous.
Evaluated by: mr-cal-bot
Impact:
42
Quick Win:
15
Complexity:
52
Confidence:
91
Actionability:
72
Issue body
### What needs to get done
The base application class should have a mandatory `issues_page` field (or similar) to be consumed by error messages.
### Why it needs to get done
This feature would help applications direct users to the desired platform for issues and make it easier for them to report bugs.
Spawned by [this PR comment](https://github.com/canonical/craft-application/pull/701#discussion_r2017586193).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
15
Complexity:
52
Confidence:
91
Actionability:
72
|
needs triage | Open, untriaged request to add a mandatory issue-reporting URL to AppMetadata; the current code exposes docs_url but has no issues_page field. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
14
Complexity:
20
Confidence:
70
Actionability:
60
|
needs triage | Feature request to add an `issues_page` field to AppMetadata for directing users to issue reporting platforms. No implementation exists yet. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
24
Staleness:
72
Complexity:
30
Confidence:
70
Support Request:
10
|
needs triage | Feature request to add a mandatory issues_page field to the base application class for use in error messages, enabling apps to direct users to their bug-report platform. Unimplemented, no labels, no comments, last activity 465 days ago. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
20
Confidence:
75
Support Request:
10
|
needs triage | Feature request to add a mandatory issues_page field to the base application class for directing users to bug reporting platforms. Unlabelled and inactive for over 16 months. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
35
Confidence:
85
Support Request:
10
|
needs triage | Feature request to add a mandatory issues_page field to the base application class for directing users to bug reporting platforms. Currently unlabelled and inactive for over a year with no maintainer discussion. |
Update history
No update history recorded yet.
Related work
-
Caused By:
canonical/craft-application#701
(confidence 99%)
The issue explicitly says it was spawned by a comment in PR #701.
Related issues
No related issues found above the similarity threshold.