Have change procedure make the issue status of "closed" mean "merged to master"

USE CASE: WHAT DO YOU WANT TO DO?

Know which issues are ready for testing.

STEPS TO REPRODUCE AN ISSUE (OR TRIGGER A NEW FEATURE)

Test a jar file
Search completed bitbucket issues to test the jar for correctness of issue handling
Note that resolved issues are not always reflected in the jar file

CURRENT BEHAVIOR

Resolved/closed statuses on BB issues do not indicate whether a resolved issue has been merged to master, hence there's no way to tell which issues are ready for testing.

EXPECTED BEHAVIOR

Resolved = a fix exists in a feature branch for the issue. Closed = a resolved feature fix has been merged to master. The tester should be able to look at all closed issued (closed before the date of the generation of the jar) and proceed with testing.

DEVELOPERS ONLY SECTION

SUGGESTED CHANGE (Pseudocode optional)

Add a step in the change procedure to close an issue after merge with master.

FILES AFFECTED (where the changes will be implemented) - developers only

SCMP

LEVEL OF EFFORT - developers only

trivial

COMMENTS

Comments (3)