Open RickJWagner opened 6 years ago
@aslakknutsen @bartoszmajsak what do you think. My first thought is to use the work items number like github does with the hash sign. I don't know what you have planned though.
@joshuawilson Jira with Bitbucket, GitHub, GitLab - they use the same convention. Why should we re-invent the wheel if that's a common and well-known thing known as #hashtag
? ;)
I wasn't asking if you liked the idea but if you planned to implement it? :)
@openshiftio/uxd-team please evaluate this request.
Based on a conversation held on 2019-Jan-04 including Dev, PM and UX, the UX team will not be providing support for planner items. Closing this issue since this was solely around gathering requirements.
When using tools like JIRA or Bugzilla to track issues, source control log messages often contain hyperlinks back to the originating issue. (At the least, a discrete issue tracking number is often used to allow the code reviewer to tie the work back to the issue that caused it.)
How is this done using our planning tool? How should we decorate source control push messages so the code being committed can be tied back to an issue tracker that can be reviewed?