I would love that also! Atm we need to: * add the tag to the jira issue * add the component in the dropdown for components * add the component to the PR
In case of multiple components, the above is per component, per PR. IMO we should only have to select the component from one place, which IMO should be the component dropdown in JIRA, which has the strongest validation and is thus less prone to mistakes. >From that component field, we can derive the squashed commit name (e.g. in dev/merge_pr.py, read from it and use it to create the commit message), and also use it to populate the changelog accordingly. My concern with a jira bot is that people are already heavily spammed by JIRA. On a new PR, this is roughly my email activity: * email from github with the bot adding the link to jira * email from JIRA with an update that the bot added a link to jira [if I forgot to place the jira issue] * email from github with the bot adding the message about a missing jira issue * email from JIRA with an update that the bot added a message about a missing jira issue [if forgot to place the jira issue] * email from github with coverage * email from JIRA with an update that the bot added coverage report * email from github that someone commented/reviewed etc * email from JIRA with an update that someone commented/reviewed etc * [repeat for every activity on the PR] imo this is way too much verbosity, specially the github+JIRA with copies of each other. If we start changing titles on JIRA, there will be yet another email from JIRA with that update. Note that emails from JIRA are administered globally on the project, the email from github for updates on the PR is imo way more relevant (because it is a one-click from email to the exact comment). I suspect that many people either ignore JIRA, or have some filter to ignore it, which imo is bad because important discussions do happen in JIRA - they are just a needle in the haystack (I am curious as to whether folks have a different setup here!) Regardless, I am up to pair with you Neal to work on this front to alleviate this if others also feel some pain with this. Best, Jorge On Fri, Feb 5, 2021 at 5:19 PM Neal Richardson <neal.p.richard...@gmail.com> wrote: > I am all for automation. I'll see if I can carve out some time to work on > that next week. > > Neal > > On Fri, Feb 5, 2021 at 8:13 AM Wes McKinney <wesmck...@gmail.com> wrote: > > > It occurs to me we could (relatively) easily program a bot to apply > > these "title tags" automatically based on what's in the Component > > field. What do you think? > > > > On Fri, Feb 5, 2021 at 10:09 AM Neal Richardson > > <neal.p.richard...@gmail.com> wrote: > > > > > > Hi folks, > > > Just a reminder to please make sure your JIRA issue titles start with > the > > > subproject/language in square brackets ([Rust], [Python], etc.). If > > you're > > > reviewing or triaging issues that others have reported, please do clean > > > them up. While it is technically redundant to the component field, it > is > > > greatly helpful for being able to scan the JIRA activity feed, and it's > > > important for making our changelogs readable. > > > > > > Thanks, > > > Neal > > >
