So, to sum up and to try to progress on this topic:
- JIRA is a tool to list tasks needed for a given release. It’s not supposed to be related to source code changes only. JIRA has a roadmap feature to list all issues needed or fixed for a given roadmap. Thus it’s normal and expected to mix issues with different outcomes (code outcome, doc outcome, design.xwiki.org outcome, etc).
- We already have a component named “Development issues only” used for issues that are for development and not interesting for end users (ie that should not appear in our release notes)
- JIRA offers a plugin to link jira issues with code commits (and we use it). There’s even the ability to use JQL to list issues with code commits or not in case we want to query that.
- We already have labels to differentiate domains for issues (ui, security, etc).
- It’s not because an issue doesn’t lead to a commit that it cannot have a fix version. Any issue needs to be organized and target a given release. That’s what a roadmap is for.
I hope that this addresses the comments from @tmortagne and @surli in this thread.
In view of this, could we come up with an agreement:
A) about Allow creating JIRA issues not related to code in any JIRA project (please reply there)
B) that we’re ok to use the existing Development issue only component + existing labels, even for development issues that don’t need a commit in the source repo? And to use that for issues for design work.
Thanks