-
Task
-
Resolution: Done
-
Critical
-
2.8.0.GA
-
False
-
False
-
Undefined
-
As we are now using the new¬eworthy label to identify new features and known issues being released in Che, we can use that to generate CRW (and RHDEVDOCS?) issues where we set:
- for GH issue milestone x or y, set JIRA fixversion z [need mapping table]
- for GH issue label "new¬eworthy", set JIRA label "noteworthy"
- set JIRA field re: Release Notes Text to "To be written by team lead or assignee"
- set JIRA field re: Release Notes Docs Status to be "Not Yet Documented" (or whatever value Docs team uses in queries)
We could take https://github.com/redhat-developer/codeready-workspaces-jiralint/blob/master/bzira.py#L44 and spawn a variant that supports upstream GH issues instead of Bugzilla, for creation of duplicate JIRAs associated w/ N&N Che issues.
- is depended on by
-
CRW-3830 improvements to ghira bot / release notes automation
- Closed
- is related to
-
RHDEVDOCS-2808 Automate synchronization between GH and Jira
- Closed
- relates to
-
CRW-3882 enable jiralint for CRW JIRA
- Closed
- mentioned on