Skip to content
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

Closed
atodorov opened this issue Jan 7, 2019 · 2 comments
Closed

RFC: Bug-tracker functionality inside Kiwi TCMS #699

atodorov opened this issue Jan 7, 2019 · 2 comments

Comments

@atodorov
Copy link
Member

@atodorov atodorov commented Jan 7, 2019

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.

@okainov
Copy link
Contributor

@okainov okainov commented Jan 8, 2019

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.

@kryskool
Copy link
Contributor

@kryskool kryskool commented Jan 16, 2019

Hi @atodorov

Why don't use entry_point to allow plugin creation ?

We must convert existing plugins to a separate plugin with name like

  • ktcms-plugin-issuetracker-github
  • ktcms-plugin-issuetracker-jira

You can see an example at this address and this one

Regards

@atodorov atodorov added this to the bug-tracker integration milestone Jul 30, 2019
atodorov added a commit that referenced this issue Sep 4, 2019
atodorov added a commit that referenced this issue Sep 10, 2019
atodorov added a commit that referenced this issue Sep 18, 2019
a very minimalistic bug tracker for the ones who need it
atodorov added a commit that referenced this issue Sep 18, 2019
which are hooked up into the bug display page

NOTE: these methods are available only if tcms.bugs is enabled in
INSTALLED_APPS
atodorov added a commit that referenced this issue Sep 18, 2019
because there can be many comments and on smaller screens the rest
of the widgets will be harder to reach.
atodorov added a commit that referenced this issue Sep 18, 2019
- [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.
atodorov added a commit that referenced this issue Sep 18, 2019
- 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
atodorov added a commit that referenced this issue Sep 18, 2019
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.
atodorov added a commit that referenced this issue Sep 19, 2019
atodorov added a commit that referenced this issue Sep 19, 2019
- also add Bug.filter() API function
atodorov added a commit that referenced this issue Sep 19, 2019
a very minimalistic bug tracker for the ones who need it
atodorov added a commit that referenced this issue Sep 19, 2019
which are hooked up into the bug display page

NOTE: these methods are available only if tcms.bugs is enabled in
INSTALLED_APPS
atodorov added a commit that referenced this issue Sep 19, 2019
because there can be many comments and on smaller screens the rest
of the widgets will be harder to reach.
atodorov added a commit that referenced this issue Sep 19, 2019
- [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.
atodorov added a commit that referenced this issue Sep 19, 2019
- 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
atodorov added a commit that referenced this issue Sep 19, 2019
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.
atodorov added a commit that referenced this issue Sep 19, 2019
- also add Bug.filter() API function
@atodorov atodorov closed this in 89899a5 Sep 19, 2019
atodorov added a commit that referenced this issue Sep 19, 2019
which are hooked up into the bug display page

NOTE: these methods are available only if tcms.bugs is enabled in
INSTALLED_APPS
atodorov added a commit that referenced this issue Sep 19, 2019
because there can be many comments and on smaller screens the rest
of the widgets will be harder to reach.
atodorov added a commit that referenced this issue Sep 19, 2019
- [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.
atodorov added a commit that referenced this issue Sep 19, 2019
- 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
atodorov added a commit that referenced this issue Sep 19, 2019
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.
atodorov added a commit that referenced this issue Sep 19, 2019
- also add Bug.filter() API function
SvetlomirBalevski added a commit to SvetlomirBalevski/Kiwi that referenced this issue Sep 24, 2019
a very minimalistic bug tracker for the ones who need it
SvetlomirBalevski added a commit to SvetlomirBalevski/Kiwi that referenced this issue Sep 24, 2019
which are hooked up into the bug display page

NOTE: these methods are available only if tcms.bugs is enabled in
INSTALLED_APPS
SvetlomirBalevski added a commit to SvetlomirBalevski/Kiwi that referenced this issue Sep 24, 2019
because there can be many comments and on smaller screens the rest
of the widgets will be harder to reach.
SvetlomirBalevski added a commit to SvetlomirBalevski/Kiwi that referenced this issue Sep 24, 2019
- [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.
SvetlomirBalevski added a commit to SvetlomirBalevski/Kiwi that referenced this issue Sep 24, 2019
- 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
SvetlomirBalevski added a commit to SvetlomirBalevski/Kiwi that referenced this issue Sep 24, 2019
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.
SvetlomirBalevski added a commit to SvetlomirBalevski/Kiwi that referenced this issue Sep 24, 2019
- also add Bug.filter() API function
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants