Hey all
Hopefully someone has got a good way of doing this that is somewhat automated or at least 'less' manual. In my company we keep and Issue Log of various issues.
For example see below something like what we have.
[TABLE="class: grid, width: 500, align: left"]
<tbody>[TR]
[TD]ID[/TD]
[TD]Raised By[/TD]
[TD]Category[/TD]
[TD]Issue Details[/TD]
[TD]Reviewer Response[/TD]
[TD]Status[/TD]
[/TR]
[TR]
[TD]001[/TD]
[TD]Joe Blogs[/TD]
[TD]Code[/TD]
[TD]The code is wrong at section 2.1.5[/TD]
[TD]No it's not please provide more details[/TD]
[TD]Open[/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
</tbody>[/TABLE]
You can see that someone raises a comment, and then pending review of the 'Reviewer Response' the raiser will change the status from open to closed.
However the problem occurs when the 'Reviewer Response' does not allow us to close the issue and they come back with a question or they state it is not an issue when it still is. Up to know people will just edit the existing issue and add their initials and a new comment below the original issue. But you can imagine after multiple review rounds how messy things get.
[TABLE="class: grid, width: 500, align: left"]
<tbody>[TR]
[TD]ID[/TD]
[TD]Raised By[/TD]
[TD]Category[/TD]
[TD]Issue Details[/TD]
[TD]Reviewer Response[/TD]
[TD]Status[/TD]
[/TR]
[TR]
[TD]001[/TD]
[TD]Joe Blogs[/TD]
[TD]Code[/TD]
[TD]The code is wrong at section 2.1.5[/TD]
[TD]No it's not please provide more details[/TD]
[TD]Open[/TD]
[/TR]
[TR]
[TD]001.01[/TD]
[TD]Joe Blogs[/TD]
[TD]Code[/TD]
[TD]The code at section 2.1.5 is wrong at sub-section 7.8 for sub-routine 27[/TD]
[TD][/TD]
[TD]Open[/TD]
[/TR]
</tbody>[/TABLE]
Above is what I was thinking, rather than editing the original issue, that we just make a brand new issue with the ID suffixed with .xx and now when we filter on ID=001 we can select all versions of 001 and see the history all together.
Anyone got a good way to do something like this or an alternative, 'Track Changes' is not an open, mainly because it's terrible
Thanks
Colm
Hopefully someone has got a good way of doing this that is somewhat automated or at least 'less' manual. In my company we keep and Issue Log of various issues.
For example see below something like what we have.
[TABLE="class: grid, width: 500, align: left"]
<tbody>[TR]
[TD]ID[/TD]
[TD]Raised By[/TD]
[TD]Category[/TD]
[TD]Issue Details[/TD]
[TD]Reviewer Response[/TD]
[TD]Status[/TD]
[/TR]
[TR]
[TD]001[/TD]
[TD]Joe Blogs[/TD]
[TD]Code[/TD]
[TD]The code is wrong at section 2.1.5[/TD]
[TD]No it's not please provide more details[/TD]
[TD]Open[/TD]
[/TR]
[TR]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[TD][/TD]
[/TR]
</tbody>[/TABLE]
You can see that someone raises a comment, and then pending review of the 'Reviewer Response' the raiser will change the status from open to closed.
However the problem occurs when the 'Reviewer Response' does not allow us to close the issue and they come back with a question or they state it is not an issue when it still is. Up to know people will just edit the existing issue and add their initials and a new comment below the original issue. But you can imagine after multiple review rounds how messy things get.
[TABLE="class: grid, width: 500, align: left"]
<tbody>[TR]
[TD]ID[/TD]
[TD]Raised By[/TD]
[TD]Category[/TD]
[TD]Issue Details[/TD]
[TD]Reviewer Response[/TD]
[TD]Status[/TD]
[/TR]
[TR]
[TD]001[/TD]
[TD]Joe Blogs[/TD]
[TD]Code[/TD]
[TD]The code is wrong at section 2.1.5[/TD]
[TD]No it's not please provide more details[/TD]
[TD]Open[/TD]
[/TR]
[TR]
[TD]001.01[/TD]
[TD]Joe Blogs[/TD]
[TD]Code[/TD]
[TD]The code at section 2.1.5 is wrong at sub-section 7.8 for sub-routine 27[/TD]
[TD][/TD]
[TD]Open[/TD]
[/TR]
</tbody>[/TABLE]
Above is what I was thinking, rather than editing the original issue, that we just make a brand new issue with the ID suffixed with .xx and now when we filter on ID=001 we can select all versions of 001 and see the history all together.
Anyone got a good way to do something like this or an alternative, 'Track Changes' is not an open, mainly because it's terrible
Thanks
Colm
Last edited: