Issue Workflow - General development

BugNET Forums

Forum Development General develop... Issue Workflow

5/11/2008 6:59 PM

	Doug
2 posts

Issue Workflow

There are a couple of features that are missing in BugNet that I have seen in commercial programs that I think would be beneficial. The main one is an Issue Workflow, which makes sure that an issue flows through the system in a predictable way. What I mean by this, is that it will limit what you can see or do depending on what roles you are in. The workflow should be completly configurable.

If you are a developer, it might only allow you to select Resolved from the status, and Closed isn't an option. This might be because the person doing testing only looks for issues in the resolved status, and they move it to closed after testing is successful.

Or if you are a customer, create a new role called Customer and hide the Assigned To field and Comments, and make the Status read only. This would allow them to see what is important, but not the internal information they don't need, and it would stop them from reopening an issue directly, instead of notifing the project manager and having them reopen it.

One way this could be implemented is to expand on the Role security screen, and add an option for the fields to limit. Each field, if it makes sense for that field, will have checkboxes for Visible, Add New, Change, and a listbox to select what values to display.

There is another thread requesting a Customer Portal, http://www.bugnetproject.com/Forums/tabid/54/forumid/-1/threadid/1670/scope/posts/Default.aspx, I think the Issue Workflow would fullfill that request as well.

At the moment I don't have a lot of time to work on this, but I wanted to put the idea out there and see what others thought. If my time frees up, and no one else has started this, I will attempt to code it.

Doug

5/12/2008 12:16 PM

	admin
544 posts
bugnetproject.com

Re: Issue Workflow

Hi Doug,

Thanks for the great post. I have thought about BugNET having custom definable workflows a bit and often consider this type of functionalty the icing on the cake for the issue tracker before we hit version 1.0. I pictured this functionality to be similar to jira or mingle where you could define custom transitions between states of an issue. Unfortunatly, there is so much on the plate right now that it might be awhile before I personally can get to doing this.

There are a great wealth of new features coming that will make BugNET a much more rounded product but I agree with you that this feature is missing and would be beneficial.

If you have some time to donate to work on this it would be greatly appreciated, even if it is providing design and thoughts on how it should work like you have here is a great start.

Davin Dubeau
BugNET - Core Developer

Page 1 of 1

Forum

Development

General develop...

Issue Workflow

Forum Policy

These Discussion Forums are dedicated to the discussion of the BugNET issue tracker.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:
1. No Advertising.
2. No Flaming or Trolling.
3. No Profanity, Racism, or Prejudice.
4. Site Moderators have the final word on approving/removing a thread or post or comment.
5. English language posting only, please.