-
-
Notifications
You must be signed in to change notification settings - Fork 299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC: Bug-tracker functionality inside Kiwi TCMS #699
Comments
There are dozens of small free and even open-source bug trackers (see MantisBT for example). Implementation of your own wheel seems like a big overhead with extra maintenance afterwards. Also I assume that target audience of Kiwi is not the small team of 5 people who just started project\startup yesterday, so they don't have any tools and processes in place (?). I believe, if the team is mature to introduce test management, they should already have bug tracking set up and running. Having said that, it seems much more useful to support more of existing bug trackers to be able to integrate with Kiwi, instead of writing your own. However, if you want Kiwi to go beyond TCMS in general, you may consider making some kind if plugins\extensions (in separated repos, with separated codebase), and here some basic bug tracker functionality could be an okay-idea for extension. So if one wants to install it, one can go to, lets say, admin panel - plugins - bug tracker - activate - and get it automagically. |
Hi @atodorov Why don't use entry_point to allow plugin creation ? We must convert existing plugins to a separate plugin with name like
You can see an example at this address and this one Regards |
a very minimalistic bug tracker for the ones who need it
which are hooked up into the bug display page NOTE: these methods are available only if tcms.bugs is enabled in INSTALLED_APPS
because there can be many comments and on smaller screens the rest of the widgets will be harder to reach.
- [db] add db_index=True to LinkReference.url field - modify TC Executions card to show bugs only when specified. When viewing the Bug page showing the same info again doesn't give us any more additional information but occupies screen space.
- moved IssueTrackerType into a base module to simplify types.py - renamed IssueTrackerType.from_name() as types.from_name() - IssueTrackerType.report_issue_from_testexecution() now has a second parameter ``user`` - added tcms.bugs.views.New.create_bug() helper method which also tries to automatically find assignee - added kiwitcms.py which doesn't go via the RPC layer but instead works internally - API method TestExecution.add_link() special cases this new IT and always updates the references between Bug & TestExecution models - when clicking 'Report bug' from inside TestExecution the new bug is reported automatically and new browser window opens to display the bug information - OpenGraph support for bugs/get.html template
a closed bug doesn't allow any more comments. User will have to open a new one if the issue still persists. This should be very easy to do when opening from a TE since everything is automated.
- also add Bug.filter() API function
a very minimalistic bug tracker for the ones who need it
which are hooked up into the bug display page NOTE: these methods are available only if tcms.bugs is enabled in INSTALLED_APPS
because there can be many comments and on smaller screens the rest of the widgets will be harder to reach.
- [db] add db_index=True to LinkReference.url field - modify TC Executions card to show bugs only when specified. When viewing the Bug page showing the same info again doesn't give us any more additional information but occupies screen space.
- moved IssueTrackerType into a base module to simplify types.py - renamed IssueTrackerType.from_name() as types.from_name() - IssueTrackerType.report_issue_from_testexecution() now has a second parameter ``user`` - added tcms.bugs.views.New.create_bug() helper method which also tries to automatically find assignee - added kiwitcms.py which doesn't go via the RPC layer but instead works internally - API method TestExecution.add_link() special cases this new IT and always updates the references between Bug & TestExecution models - when clicking 'Report bug' from inside TestExecution the new bug is reported automatically and new browser window opens to display the bug information - OpenGraph support for bugs/get.html template
a closed bug doesn't allow any more comments. User will have to open a new one if the issue still persists. This should be very easy to do when opening from a TE since everything is automated.
- also add Bug.filter() API function
which are hooked up into the bug display page NOTE: these methods are available only if tcms.bugs is enabled in INSTALLED_APPS
because there can be many comments and on smaller screens the rest of the widgets will be harder to reach.
- [db] add db_index=True to LinkReference.url field - modify TC Executions card to show bugs only when specified. When viewing the Bug page showing the same info again doesn't give us any more additional information but occupies screen space.
- moved IssueTrackerType into a base module to simplify types.py - renamed IssueTrackerType.from_name() as types.from_name() - IssueTrackerType.report_issue_from_testexecution() now has a second parameter ``user`` - added tcms.bugs.views.New.create_bug() helper method which also tries to automatically find assignee - added kiwitcms.py which doesn't go via the RPC layer but instead works internally - API method TestExecution.add_link() special cases this new IT and always updates the references between Bug & TestExecution models - when clicking 'Report bug' from inside TestExecution the new bug is reported automatically and new browser window opens to display the bug information - OpenGraph support for bugs/get.html template
a closed bug doesn't allow any more comments. User will have to open a new one if the issue still persists. This should be very easy to do when opening from a TE since everything is automated.
- also add Bug.filter() API function
a very minimalistic bug tracker for the ones who need it
which are hooked up into the bug display page NOTE: these methods are available only if tcms.bugs is enabled in INSTALLED_APPS
because there can be many comments and on smaller screens the rest of the widgets will be harder to reach.
- [db] add db_index=True to LinkReference.url field - modify TC Executions card to show bugs only when specified. When viewing the Bug page showing the same info again doesn't give us any more additional information but occupies screen space.
- moved IssueTrackerType into a base module to simplify types.py - renamed IssueTrackerType.from_name() as types.from_name() - IssueTrackerType.report_issue_from_testexecution() now has a second parameter ``user`` - added tcms.bugs.views.New.create_bug() helper method which also tries to automatically find assignee - added kiwitcms.py which doesn't go via the RPC layer but instead works internally - API method TestExecution.add_link() special cases this new IT and always updates the references between Bug & TestExecution models - when clicking 'Report bug' from inside TestExecution the new bug is reported automatically and new browser window opens to display the bug information - OpenGraph support for bugs/get.html template
a closed bug doesn't allow any more comments. User will have to open a new one if the issue still persists. This should be very easy to do when opening from a TE since everything is automated.
- also add Bug.filter() API function
There's an idea for Kiwi TCMS to be able to keep track of reported bugs directly inside the system. The functionality will be minimal, similar to what GitHub Issues provides. This will be useful to small teams who do no need tons of functionality (sort of like JIRA) or do not want to deploy a separate system for bug-tracking.
Please vote with a 👍 reaction (top-right corner) if you find a feature like that useful!
Use the comments below to describe the features and behavior you imagine this bug-tracker to have.
The text was updated successfully, but these errors were encountered: