Use bug tracker integration to show bugs details #117
Labels
Milestone
Comments
|
This is a reasonable request. Do you prefer to store the names in the database where they can get out of sync with the bug tracker or to fetch the names when we display the bugs (possibly slowing down b/c we have to talk to an external system)? |
|
As for the moment, any page related to bug trackers is being loaded pretty slow, because JIRA.jira (we use this bug tracker) object is initialized every time from scratch. So it's not very fast anyway =) |
|
Hi i just created a github account and then i used same login credentials for using kiwitcms. I created Test plan,Test cases, Test runs.. But i am not able link JIRA tickets to the test cases. I am able to Add jira ticket by clicking on ADD under Bug, but when i click on the ticket number it is showing you need to Enable linking test cases by configuring API parameters for this Issue Tracker! Please help me out in this issue. |
atodorov
added a commit
that referenced
this issue
Aug 27, 2019
this method together with the underlying IssueTracker.details() will be the foundation of how Kiwi TCMS fetches more details from the bug tracking system. At the moment the intention is for this information to be shown in the UI but it can also be consumed independently via the API. By default we're using OpenGraph protocol to collect the data that will be shown. The details() method can be overriden for each bug tracker that is supported and you may also override the entire class with something you have created yourself.
atodorov
added a commit
that referenced
this issue
Aug 27, 2019
- added to TestCase page, Executions card, will execute on click - added to TestCase page, Bugs card - use client side caching as well b/c the same bugs may be shown multiple times in the same page. If data has already been fetched then use it TODO: - add to TestRun page, TE details
atodorov
added a commit
that referenced
this issue
Aug 27, 2019
this method together with the underlying IssueTracker.details() will be the foundation of how Kiwi TCMS fetches more details from the bug tracking system. At the moment the intention is for this information to be shown in the UI but it can also be consumed independently via the API. By default we're using OpenGraph protocol to collect the data that will be shown. The details() method can be overriden for each bug tracker that is supported and you may also override the entire class with something you have created yourself.
atodorov
added a commit
that referenced
this issue
Aug 27, 2019
- added to TestCase page, Executions card, will execute on click - added to TestCase page, Bugs card - use client side caching as well b/c the same bugs may be shown multiple times in the same page. If data has already been fetched then use it TODO: - add to TestRun page, TE details
atodorov
added a commit
that referenced
this issue
Aug 27, 2019
- added to TestCase page, Executions card, will execute on click - added to TestCase page, Bugs card - use client side caching as well b/c the same bugs may be shown multiple times in the same page. If data has already been fetched then use it - update TE widget in TR page to show timestamp | del btn. Later will show an info button here as well. NOTE: - adding bug details to TestRun page, TE widget needs Patternfly popovers and is best to be done when the entire page has been redesigned to the new UI
atodorov
added a commit
that referenced
this issue
Aug 27, 2019
this method together with the underlying IssueTracker.details() will be the foundation of how Kiwi TCMS fetches more details from the bug tracking system. At the moment the intention is for this information to be shown in the UI but it can also be consumed independently via the API. By default we're using OpenGraph protocol to collect the data that will be shown. The details() method can be overriden for each bug tracker that is supported and you may also override the entire class with something you have created yourself.
atodorov
added a commit
that referenced
this issue
Aug 27, 2019
- added to TestCase page, Executions card, will execute on click - added to TestCase page, Bugs card - use client side caching as well b/c the same bugs may be shown multiple times in the same page. If data has already been fetched then use it - update TE widget in TR page to show timestamp | del btn. Later will show an info button here as well. NOTE: - adding bug details to TestRun page, TE widget needs Patternfly popovers and is best to be done when the entire page has been redesigned to the new UI
atodorov
added a commit
that referenced
this issue
Aug 28, 2019
this method together with the underlying IssueTracker.details() will be the foundation of how Kiwi TCMS fetches more details from the bug tracking system. At the moment the intention is for this information to be shown in the UI but it can also be consumed independently via the API. By default we're using OpenGraph protocol to collect the data that will be shown. The details() method can be overriden for each bug tracker that is supported and you may also override the entire class with something you have created yourself.
atodorov
added a commit
that referenced
this issue
Aug 28, 2019
- added to TestCase page, Executions card, will execute on click - added to TestCase page, Bugs card - use client side caching as well b/c the same bugs may be shown multiple times in the same page. If data has already been fetched then use it - update TE widget in TR page to show timestamp | del btn. Later will show an info button here as well. NOTE: - adding bug details to TestRun page, TE widget needs Patternfly popovers and is best to be done when the entire page has been redesigned to the new UI
atodorov
added a commit
that referenced
this issue
Aug 28, 2019
this method together with the underlying IssueTracker.details() will be the foundation of how Kiwi TCMS fetches more details from the bug tracking system. At the moment the intention is for this information to be shown in the UI but it can also be consumed independently via the API. By default we're using OpenGraph protocol to collect the data that will be shown. The details() method can be overriden for each bug tracker that is supported and you may also override the entire class with something you have created yourself.
atodorov
added a commit
that referenced
this issue
Aug 28, 2019
- added to TestCase page, Executions card, will execute on click - added to TestCase page, Bugs card - use client side caching as well b/c the same bugs may be shown multiple times in the same page. If data has already been fetched then use it - update TE widget in TR page to show timestamp | del btn. Later will show an info button here as well. NOTE: - adding bug details to TestRun page, TE widget needs Patternfly popovers and is best to be done when the entire page has been redesigned to the new UI
atodorov
added a commit
that referenced
this issue
Aug 28, 2019
this method together with the underlying IssueTracker.details() will be the foundation of how Kiwi TCMS fetches more details from the bug tracking system. At the moment the intention is for this information to be shown in the UI but it can also be consumed independently via the API. By default we're using OpenGraph protocol to collect the data that will be shown. The details() method can be overriden for each bug tracker that is supported and you may also override the entire class with something you have created yourself.
atodorov
added a commit
that referenced
this issue
Aug 28, 2019
- added to TestCase page, Executions card, will execute on click - added to TestCase page, Bugs card - use client side caching as well b/c the same bugs may be shown multiple times in the same page. If data has already been fetched then use it - update TE widget in TR page to show timestamp | del btn. Later will show an info button here as well. NOTE: - adding bug details to TestRun page, TE widget needs Patternfly popovers and is best to be done when the entire page has been redesigned to the new UI
atodorov
added a commit
that referenced
this issue
Sep 3, 2019
this method together with the underlying IssueTracker.details() will be the foundation of how Kiwi TCMS fetches more details from the bug tracking system. At the moment the intention is for this information to be shown in the UI but it can also be consumed independently via the API. By default we're using OpenGraph protocol to collect the data that will be shown. The details() method can be overriden for each bug tracker that is supported and you may also override the entire class with something you have created yourself.
atodorov
added a commit
that referenced
this issue
Sep 3, 2019
- added to TestCase page, Executions card, will execute on click - added to TestCase page, Bugs card - use client side caching as well b/c the same bugs may be shown multiple times in the same page. If data has already been fetched then use it - update TE widget in TR page to show timestamp | del btn. Later will show an info button here as well. NOTE: - adding bug details to TestRun page, TE widget needs Patternfly popovers and is best to be done when the entire page has been redesigned to the new UI
atodorov
added a commit
that referenced
this issue
Sep 4, 2019
this method together with the underlying IssueTracker.details() will be the foundation of how Kiwi TCMS fetches more details from the bug tracking system. At the moment the intention is for this information to be shown in the UI but it can also be consumed independently via the API. By default we're using OpenGraph protocol to collect the data that will be shown. The details() method can be overriden for each bug tracker that is supported and you may also override the entire class with something you have created yourself.
atodorov
added a commit
that referenced
this issue
Sep 4, 2019
- added to TestCase page, Executions card, will execute on click - added to TestCase page, Bugs card - use client side caching as well b/c the same bugs may be shown multiple times in the same page. If data has already been fetched then use it - update TE widget in TR page to show timestamp | del btn. Later will show an info button here as well. NOTE: - adding bug details to TestRun page, TE widget needs Patternfly popovers and is best to be done when the entire page has been redesigned to the new UI
atodorov
added a commit
that referenced
this issue
Sep 13, 2019
this method together with the underlying IssueTracker.details() will be the foundation of how Kiwi TCMS fetches more details from the bug tracking system. At the moment the intention is for this information to be shown in the UI but it can also be consumed independently via the API. By default we're using OpenGraph protocol to collect the data that will be shown. The details() method can be overriden for each bug tracker that is supported and you may also override the entire class with something you have created yourself.
atodorov
added a commit
that referenced
this issue
Sep 13, 2019
- added to TestCase page, Executions card, will execute on click - added to TestCase page, Bugs card - use client side caching as well b/c the same bugs may be shown multiple times in the same page. If data has already been fetched then use it - update TE widget in TR page to show timestamp | del btn. Later will show an info button here as well. NOTE: - adding bug details to TestRun page, TE widget needs Patternfly popovers and is best to be done when the entire page has been redesigned to the new UI
atodorov
added a commit
that referenced
this issue
Sep 15, 2019
this method together with the underlying IssueTracker.details() will be the foundation of how Kiwi TCMS fetches more details from the bug tracking system. At the moment the intention is for this information to be shown in the UI but it can also be consumed independently via the API. By default we're using OpenGraph protocol to collect the data that will be shown. The details() method can be overriden for each bug tracker that is supported and you may also override the entire class with something you have created yourself.
atodorov
added a commit
that referenced
this issue
Sep 15, 2019
- added to TestCase page, Executions card, will execute on click - added to TestCase page, Bugs card - use client side caching as well b/c the same bugs may be shown multiple times in the same page. If data has already been fetched then use it - update TE widget in TR page to show timestamp | del btn. Later will show an info button here as well. NOTE: - adding bug details to TestRun page, TE widget needs Patternfly popovers and is best to be done when the entire page has been redesigned to the new UI
atodorov
added a commit
that referenced
this issue
Sep 18, 2019
this method together with the underlying IssueTracker.details() will be the foundation of how Kiwi TCMS fetches more details from the bug tracking system. At the moment the intention is for this information to be shown in the UI but it can also be consumed independently via the API. By default we're using OpenGraph protocol to collect the data that will be shown. The details() method can be overriden for each bug tracker that is supported and you may also override the entire class with something you have created yourself.
atodorov
added a commit
that referenced
this issue
Sep 18, 2019
- added to TestCase page, Executions card, will execute on click - added to TestCase page, Bugs card - use client side caching as well b/c the same bugs may be shown multiple times in the same page. If data has already been fetched then use it - update TE widget in TR page to show timestamp | del btn. Later will show an info button here as well. NOTE: - adding bug details to TestRun page, TE widget needs Patternfly popovers and is best to be done when the entire page has been redesigned to the new UI
atodorov
added a commit
that referenced
this issue
Sep 19, 2019
this method together with the underlying IssueTracker.details() will be the foundation of how Kiwi TCMS fetches more details from the bug tracking system. At the moment the intention is for this information to be shown in the UI but it can also be consumed independently via the API. By default we're using OpenGraph protocol to collect the data that will be shown. The details() method can be overriden for each bug tracker that is supported and you may also override the entire class with something you have created yourself.
atodorov
added a commit
that referenced
this issue
Sep 19, 2019
- added to TestCase page, Executions card, will execute on click - added to TestCase page, Bugs card - use client side caching as well b/c the same bugs may be shown multiple times in the same page. If data has already been fetched then use it - update TE widget in TR page to show timestamp | del btn. Later will show an info button here as well. NOTE: - adding bug details to TestRun page, TE widget needs Patternfly popovers and is best to be done when the entire page has been redesigned to the new UI
|
There is baseline implementation for this feature which provides defaults (via OpenGraph) for each issue tracker. Specific overrides for each individual issue tracker type (e.g. Jira, Bugzilla) may be provided (either modifying the app) or as additional features later. There is both server side cache (can be anything, Django is flexible in this regard; can be used instead of DB from an external script that syncs the information) and browser side cache to try speeding up these operations. Closing. Anything else is out of scope for this particular issue. |
SvetlomirBalevski
pushed a commit
to SvetlomirBalevski/Kiwi
that referenced
this issue
Sep 24, 2019
this method together with the underlying IssueTracker.details() will be the foundation of how Kiwi TCMS fetches more details from the bug tracking system. At the moment the intention is for this information to be shown in the UI but it can also be consumed independently via the API. By default we're using OpenGraph protocol to collect the data that will be shown. The details() method can be overriden for each bug tracker that is supported and you may also override the entire class with something you have created yourself.
SvetlomirBalevski
pushed a commit
to SvetlomirBalevski/Kiwi
that referenced
this issue
Sep 24, 2019
- added to TestCase page, Executions card, will execute on click - added to TestCase page, Bugs card - use client side caching as well b/c the same bugs may be shown multiple times in the same page. If data has already been fetched then use it - update TE widget in TR page to show timestamp | del btn. Later will show an info button here as well. NOTE: - adding bug details to TestRun page, TE widget needs Patternfly popovers and is best to be done when the entire page has been redesigned to the new UI
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of problem
There is bug tracker integration, but looks like it's almost not used. At least I would expect to see bugs names in runs or reports, not just ID with link
Component (web, API, etc)
WEB
The text was updated successfully, but these errors were encountered: