Skip to content

Changes

Page history
Update gitlab roadmap authored by bgm's avatar bgm
Hide whitespace changes
Inline Side-by-side
gitlab-roadmap.md
View page @ d284d5c1
...@@ -195,7 +195,9 @@ To be clear, we do hope to migrate more than the current 39 confirmed issues. Th ...@@ -195,7 +195,9 @@ To be clear, we do hope to migrate more than the current 39 confirmed issues. Th
Stack Exchange is the front-line of support. Sometimes the answer is "this is a bug, therefore it needs to be tracked in an issue". As with JIRA, we will discourage people from opening support requests in Gitlab. Stack Exchange is the front-line of support. Sometimes the answer is "this is a bug, therefore it needs to be tracked in an issue". As with JIRA, we will discourage people from opening support requests in Gitlab.
## Won't the separate issue trackers confuse users? what about overlap? ## (duplicate) Won't the separate issue trackers confuse users? what about overlap?
*(fixme: needs to be merged with one of the points above)*
> Ex: a receipt for an event registration shows an incorrect amount. Should this be filed in the 'event', 'contribution', 'accounting' or 'civimail' project? Actually, neither because this is probably just a token issue so should be filed in the 'core' project. [ref](https://lab.civicrm.org/infrastructure/ops/issues/817#note_2799) > Ex: a receipt for an event registration shows an incorrect amount. Should this be filed in the 'event', 'contribution', 'accounting' or 'civimail' project? Actually, neither because this is probably just a token issue so should be filed in the 'core' project. [ref](https://lab.civicrm.org/infrastructure/ops/issues/817#note_2799)
......