mudita
Development workflow: Additional Github/JIRA action(s) needed.
⚠️ Development workflow
📝 Description
As far as I can tell, a community pull request requires both a manual request for a ticket by the community member as well as a Mudita team member to manually create a JIRA ticket. Since Github generates an overbearing number of notifications, a request for a ticket number can easily be (or perceived as being) "lost in the churn" (deleted without being seen) when weeks go by with no response at all. This requirement of manual ticket requests is harmful to community and Mudita members alike.
This is and issue as I presently have several unanswered ticket requests and I have no idea if the requests were ever seen or if they have been forgotten about.
📝 Describe the solution you'd like
There either needs to be some sort of tighter integration or a way for a community member to mark their PR as "ticket requested" that is viewable from the list of "Pull requests". Ideally Jenkins would check the build before generating this tag.
📝 Describe alternatives you've considered
- There could be a bot that automatically maintains a log of unfulfilled ticket requests that is visible under "Projects" but this is non-obvious.
- JIRA could create a ticket in automated fashion for each PR but this could be problematic.
- Making dealing with simple requests on Github part of the daily routine is an option but extremely inefficient and undesirable.
@GravisZro It has been already noticed. Currently we are looking for solutions. Thanks for good points.
