Require pull requests to have linked issues before merged

[yinonov]

This discussion describes a pursuit of setting up a workflow for exporting CAPEX information and actual work being done by devs, during a specific duration of time.

relevant information should include tickets describing PREQ (product request) and time duration measurement.

Organizations workflows usually keep duplicate tickets in management platforms (e.g. JIRA etc').

Now how does this connect to GitHub...

I'm trying to utilize issues and pull requests to reflect that information.
With the addition of project beta we can now set custom records like story points to our issues / pull request.

Which introduces the following 2 alternatives to take advantage of -

• Issues to act in behalf of PREQs and their time estimation
• PRs that represent the actual work done and probably a more accurate story point

Automating this process requires a way to enforce pull request to be linked to issues in order to be merged.

strangely I could not google up more than a few similar enquires out there...