Jira Ticket Number Validation
Problem to solve
Commits can be made with Jira ticket numbers that don't actually exist.
Sasha (Software Developer), Delaney (Development Team Lead), Parker (Product Manager)
With the existing Jira integration and Jira Development Panel integration, we can specify a regexp that will validate that a Jira ticket number is provided, but other than ensuring the correct format does not actually validate that the ticket exists in the linked Jira system, is in the open state, or is owned by the committer. This means that a developer can consistently commit with a dummy Jira ticket number.
In addition to checking the format of a Jira ticket number in a commit message this feature would allow Sidney (Systems Administrator) to set settings to
- require the integration query Jira to ensure the ticket number exists in the connected Jira system
- require the integration query Jira to ensure the ticket is in an open state in Jira
- require the integration to ensure the ticket is assigned to the user who did the commit
These three should be separate options, with 2 and 3 depending on 1. When these settings are set, if any of the queries does not return a match then the commit or push should be denied.
Permissions and Security
What does success look like, and how can we measure that?
When a commit or push is performed with a Jira ticket number that does not exist, the commit or push is denied.
What is the type of buyer?
This should be a Premium tier feature as it predominantly benefits managers/directors of larger organizations.