Re: Github Issues
I may have voiced my concerns earlier but as a user, I think that JIRA
issues are easier to follow than PRs.
- As Paul said an issue may affect more than one version.
- It may also require more than one PR to fully resolve the issue.
- Issues tend to be described in terms of a problem that the user would
recognize while PRs are most often described as what was done to fix the
problem. The JIRA could be much easier to relate to what the user is
seeing and more likely to show up in Google.
On 17/07/2018 4:53 AM, Paul Angus wrote:
We have been trialling replacing Jira with Github Issues. I think that we should have a conversation about it before it become the new standard by default.
From my perspective, I don't like it. Searching has become far more difficult, categorising has also. When there is a bug fix it can only be targeted for a single version, which makes them easy to lose track of, and when looking at milestones issues and PRs get jumbled up and people are commenting on issues when it should by the PR and vice-versa (yes I've done it too).
In summary, from an administrative point of view it causes a lot more problems than it solves.
I yield the floor to hear other people's opinions...
53 Chandos Place, Covent Garden, London WC2N 4HSUK
Artifact Software Inc
phone: 866-970-2435, ext 102