alamb edited a comment on pull request #9598: URL: https://github.com/apache/arrow/pull/9598#issuecomment-789623293
> (I meant to start that with: thanks for taking the initiative to make our processes better! ❤️) Thank you! > As an alternative approach, what if we had a GitHub Actions comment bot that would create a JIRA issue from your issue or PR? @neilrichardson, I think having the actions bot offer to create a JIRA issue for you would work great for me personally. The reason I didn't start from there was 1. Auto creating a ticket effectively removes the choice of *should* a ticket be created from the PR author and maintainer, and I worried we might create tickets accidentally for people who simply forgot the reference in the title as well as run into philosophical objections to such behavior. 2. Some surmountable but annoying technical concerns over credentials and not wanting to sort out JIRA authorization tokens / process for github bots (e.g. whose JIRA account credentials would it use, etc, who would it assign, etc.) In general, I felt the approach to adding an optional, manually acknowledged step, to `merge_pr` was a minimal change to the workflow that improved experiences (`merge_pr.py` was going to exit anyways), and left the maintainer in control of if a JIRA *should* be created. Clearly my attempt to dodge the "should we still be using JIRA" conversation failed miserably - LOL. I know of few other topics that incite such passion than engineering process and workflow tools! ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
