[Apache Bloodhound] #551: Search selectors overlap with results grid
#551: Search selectors overlap with results grid -+--- Reporter: olemis |Owner: Type: defect | Status: new Priority: major | Version: Resolution: | -+--- Under certain conditions Grid | Free text switch overlaps results . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/551 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #548: Simple ticket report fails
#548: Simple ticket report fails -+- Reporter: olemis | Owner: olemis Type: defect | Status: review Priority: blocker | Milestone: Release 6 Component: |Version: multiproduct | Keywords: sql reports, multiproduct db Resolution: | translator, trac util -+- Changes (by rjollos): * owner: rjollos = olemis * status: accepted = review Comment: (In [1492534]) Refs #548: Account for possibility that template timestamp argument could be a unicode string. --- Reassigning to Olemis for review and final confirmation of whether the issue is fixed. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/548#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #544: Inline expansion for quick ticket overlay
#544: Inline expansion for quick ticket overlay --+--- Reporter: jdreimann| Owner: matevzb Type: enhancement | Status: accepted Priority: major| Milestone: Release 6 Component: ui design|Version: Resolution: | Keywords: --+--- Comment (by olemis): Replying to [comment:10 rjollos]: (In [1492525]) Refs #544: Check for existence of `qct` variable before rendering the visible-phone Quick-ticket-create. This resolves a traceback under various circumstances that `qct` isn't passed to the template, such as when a !TracError is rendered on navigating to a non-existing ticket. I was trying to look into similar error I detected yesterday but was not sure if it was really an issue . Thanks for fixing . I haven't yet looked closely into why the `qct` variable isn't passed to the template when the !TracError is present, Depends on the exact point failure is detected and whether request could be fully post processed or not . or if that is proper behavior. However, we clearly don't get a Create ticket button: I guess that under certain circumstances there's no hope ... [...] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/544#comment:11 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] #552: Inaccurate URLs in global dashboard
#552: Inaccurate URLs in global dashboard -+--- Reporter: olemis |Owner: Type: defect | Status: new Priority: major | Version: Resolution: | -+--- Product widget (as opposite to grids) rendered in global dashboard might not render the right URLs when custom URL mappings have been deployed . Soon I'll post more details illustrating (what seems to be) the issue. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/552 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #552: Inaccurate URLs in global dashboard
#552: Inaccurate URLs in global dashboard -+- Reporter: olemis | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: custom bootstrap handlers, product | widget -+- Changes (by olemis): * keywords: = custom bootstrap handlers, product widget * owner: = nobody * component: = dashboard Old description: Product widget (as opposite to grids) rendered in global dashboard might not render the right URLs when custom URL mappings have been deployed . Soon I'll post more details illustrating (what seems to be) the issue. New description: Product widget (as opposite to grids) rendered in global dashboard might not render the right URLs once custom URL mappings have been deployed . Soon I'll post more details illustrating (what seems to be) the issue. -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/552#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #514: TracStandalone middlewares compatible with hooks
#514: TracStandalone middlewares compatible with hooks +--- Reporter: olemis | Owner: rjollos Type: task | Status: review Priority: major | Milestone: Release 6 Component: trac core |Version: Resolution: | Keywords: tracd authentication bep-0003 +--- Changes (by rjollos): * owner: = rjollos -- Ticket URL: https://issues.apache.org/bloodhound/ticket/514#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #513: HTTP protocol violation on factories misconfiguration
#513: HTTP protocol violation on factories misconfiguration ---+- Reporter: olemis| Owner: rjollos Type: defect| Status: review Priority: blocker | Milestone: Release 6 Component: multiproduct |Version: Resolution:| Keywords: hooks configuration ---+- Changes (by rjollos): * owner: = rjollos -- Ticket URL: https://issues.apache.org/bloodhound/ticket/513#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #446: Edit conflict warning messages may not be visible when not in side-by-side edit mode
#446: Edit conflict warning messages may not be visible when not in side-by-side edit mode + Reporter: rjollos| Owner: rjollos Type: defect | Status: new Priority: minor | Milestone: Release 7 Component: ui design |Version: Resolution: | Keywords: trac-1.0.2 + Changes (by rjollos): * keywords: = trac-1.0.2 * milestone: Release 6 = Release 7 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/446#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #550: Bootstrap template for error.html
#550: Bootstrap template for error.html + Reporter: rjollos| Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: ui design |Version: Resolution: | Keywords: + Description changed by jdreimann: Old description: A bootstrap template should be written to replace `error.html`. These pages should be more visually appealing: [[Image(ReportDefect.png)]] [[Image(ErrorPage.png)]] New description: A bootstrap template should be written to replace `error.html`. These pages should be more visually appealing. The error pages should also nudge users towards issues.apache.org/bloodhound instead of the trac hompage: [[Image(ReportDefect.png)]] [[Image(ErrorPage.png)]] -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/550#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] Proposals/BEP-0007 added
Page Proposals/BEP-0007 was added by jdreimann Content: ---8--8--8--8--8--8--8--8 -placeholder for Antonia's proposal- ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0007 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0007' page. If it was not you, please report to .
[Apache Bloodhound] Proposals/BEP-0008 added
Page Proposals/BEP-0008 was added by jdreimann Content: ---8--8--8--8--8--8--8--8 -placeholder for Hua's proposal- ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0008' page. If it was not you, please report to .
[Apache Bloodhound] Proposals/BEP-0009 added
Page Proposals/BEP-0009 was added by jdreimann Content: ---8--8--8--8--8--8--8--8 -placeholder for Pranay's proposal- = BEP BEP number : BEP title #overview [[PageOutline]] || '''BEP''' || BEP number || || '''Title''' || BEP title || || '''Version''' || leave blank || || '''Last-Modified''' || leave blank || || '''Author''' || Author With Email u...@dom.ain, Author Name Only, or The Bloodhound project (see [wiki:/Proposals#bep-header-preamble BEP preamble explained]) || || '''Status''' || Draft || || '''Type''' || BEP type (see [wiki:/Proposals#bep-types BEP types explained]) || || '''Content-Type''' || [wiki:PageTemplates/Proposals text/x-trac-wiki] || || '''Created''' || leave blank || || '''Post-History''' || leave blank || == Abstract #abstract Delete text in this section and add a short (~200 word) description of the technical issue being addressed. Take a look at sample abstract below This template provides a boilerplate or sample template for creating your own BEPs. In conjunction with the [wiki:/Proposals general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] , this should make it easy for you to conform your own BEPs to the format outlined below. See [#howto How to Use This Template] for further instructions. **Note**: if you are reading this template via the web, you should first try to create a new wiki page by selecting `ProposalsRst` |page template guide|. **DO NOT EDIT THIS WIKI PAGE IN ORDER TO CREATE A NEW BEP! ** If you would prefer not to use WikiFormatting markup in your BEP, please see [wiki:/Proposals/Formats/RestructuredText reStructuredText BEP guidelines]. == Motivation == The motivation is critical for BEPs that want to change the copy of ''Trac'' patched using vendor branch . It should clearly explain why the existing ''Bloodhound'' solution is inadequate to address the problem that the ''BEP'' solves. ''BEP'' submissions without sufficient motivation may be rejected outright. == Proposal #proposal The technical specification should describe any new features , detail its impact on the components architecture , mention what plugins will be included as a result , whether they are hosted by [http://trac-hacks.org trac-hacks.org] or not , and any other relevant technical subject . The specification should be detailed enough to allow competing, interoperable implementations for any of the current supported database platforms (e.g. ''SQLite'', ''Postgres'', ''MySQL'') and server technologies (e.g. ''Apache HTTPD server'', ''nginx'', ''mod_wsgi'', ''CGI'').. == Rationale #rationale The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other issue trackers or ''Trac'' hacks . The rationale should provide evidence of consensus within the community and discuss important objections or concerns raised during discussion. Take a look at sample rationale below ''BEP'' submissions come in a wide variety of forms, not all adhering to the format guidelines set forth below. Use this template, in conjunction with the [wiki:/Proposals general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines], to ensure that your ''BEP'' submission is easy to read and understand. This template allows to create BEPs and is very similar to [http://www.python.org/dev/peps/pep-0012 PEP 12] . However it has been optimized by moving long explanations to the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] . If you are interested take a look at the [?action=diffold_version=1 differences]. The goal is to redact new BEPs just by following in-line instructions between angle brackets (i.e. ) . Even if this will allow to write BEPs faster , it is highly recommended to read the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] at least once in your lifetime to be aware of good practices and expected style rules . == How to Use This Template #howto BEPs may include further sections. This is an example. Quick edits will consist in following the instructions inside angle brackets (i.e. ) . That should be everything needed to write new BEPs. To be more informed about advanced considerations please read the [wiki:/Proposals general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] . If there is no point in including one of the sections in this document then feel free to remove it. == Backwards Compatibility #backwards-compatibility All BEPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The ''BEP'' must explain how to deal with these
[Apache Bloodhound] Proposals/BEP-0007 modified
Page Proposals/BEP-0007 was changed by jdreimann Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0007?action=diffversion=2 Revision 2 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0007 = --- Proposals/BEP-0007 (version: 1) +++ Proposals/BEP-0007 (version: 2) @@ -1,1 +1,88 @@ -placeholder for Antonia's proposal- + += BEP BEP number : BEP title #overview + +[[PageOutline]] + +|| '''BEP''' || BEP number || +|| '''Title''' || BEP title || +|| '''Version''' || leave blank || +|| '''Last-Modified''' || leave blank || +|| '''Author''' || Author With Email u...@dom.ain, Author Name Only, or The Bloodhound project (see [wiki:/Proposals#bep-header-preamble BEP preamble explained]) || +|| '''Status''' || Draft || +|| '''Type''' || BEP type (see [wiki:/Proposals#bep-types BEP types explained]) || +|| '''Content-Type''' || [wiki:PageTemplates/Proposals text/x-trac-wiki] || +|| '''Created''' || leave blank || +|| '''Post-History''' || leave blank || + + + +== Abstract #abstract + +Delete text in this section and add a short (~200 word) description of the technical issue being addressed. Take a look at sample abstract below + +This template provides a boilerplate or sample template for creating your +own BEPs. In conjunction with the [wiki:/Proposals general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] +, this should make it easy for you to conform your own +BEPs to the format outlined below. See [#howto How to Use This Template] for further instructions. + +**Note**: if you are reading this template via the web, you should first try to create a new wiki page by selecting `ProposalsRst` |page template guide|. **DO NOT EDIT THIS WIKI PAGE IN ORDER TO CREATE A NEW BEP! ** + +If you would prefer not to use WikiFormatting markup in your BEP, please see [wiki:/Proposals/Formats/RestructuredText reStructuredText BEP guidelines]. + +== Motivation == + +The motivation is critical for BEPs that want to change the copy of ''Trac'' patched using vendor branch . It should clearly explain why the existing ''Bloodhound'' solution is inadequate to address the problem that the ''BEP'' solves. ''BEP'' submissions without sufficient motivation may be rejected outright. + +== Proposal #proposal + +The technical specification should describe any new features , detail its impact on the components architecture , mention what plugins will be included as a result , whether they are hosted by [http://trac-hacks.org trac-hacks.org] or not , and any other relevant technical subject . The specification should be detailed enough to allow competing, interoperable implementations for any of the current supported database platforms (e.g. ''SQLite'', ''Postgres'', ''MySQL'') and server technologies (e.g. ''Apache HTTPD server'', ''nginx'', ''mod_wsgi'', ''CGI'').. + +== Rationale #rationale + +The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other issue trackers or ''Trac'' hacks . The rationale should provide evidence of consensus within the community and discuss important objections or concerns raised during discussion. Take a look at sample rationale below + +''BEP'' submissions come in a wide variety of forms, not all adhering to the format guidelines set forth below. Use this template, in conjunction with the [wiki:/Proposals general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines], to ensure that your ''BEP'' submission is easy to read and understand. + +This template allows to create BEPs and is very similar to [http://www.python.org/dev/peps/pep-0012 PEP 12] . However it has been optimized by moving long explanations to the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] . If you are interested take a look at the [?action=diffold_version=1 differences]. The goal is to redact new BEPs just by following in-line instructions between angle brackets (i.e. ) . Even if this will allow to write BEPs faster , it is highly recommended to read the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] at least once in your lifetime to be aware of good practices and expected style rules . + +== How to Use This Template #howto + +BEPs may include further sections. This is an example. + +Quick edits will consist in following the instructions inside angle brackets (i.e. ) . That should be everything needed to write new BEPs. To be more informed about advanced considerations please read the [wiki:/Proposals general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] .
[Apache Bloodhound] Proposals/BEP-0008 deleted
Page Proposals/BEP-0008 was deleted by jdreimann -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0008' page. If it was not you, please report to .
[Apache Bloodhound] Proposals/BEP-0007 deleted
Page Proposals/BEP-0007 was deleted by jdreimann -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0007 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0007' page. If it was not you, please report to .
[Apache Bloodhound] New user registration: antonia.horincar
New user registration for user antonia.horincar -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #387: Rewrite Trac functional test cases against product environments - after #355
#387: Rewrite Trac functional test cases against product environments - after
#355
-+-
Reporter: olemis | Owner: olemis
Type: task| Status: accepted
Priority: major | Milestone:
Component: |Version:
multiproduct | Keywords: product environment functional
Resolution: | testing QA
-+-
Comment (by olemis):
Patches attached to this ticket are an early preview of the work made to
rewrite Trac functional test suite . Details below
{{{#!sh
$ hg qapplied
t509/t509_r1480735_mp_class_test_setup.diff
t509/t509_r143_tracadmin_globalcmd_attr.diff
t514/t514_r143_load_bootstrap_handler.diff
t514/t514_r143_tracd_bootstrap.diff
t387/t387_r1487712_bloodhound_setup.diff
t387/t387_r1485255_functional_test_infra.diff
$ hg log -r qparent --template=[{svnrev}] - {desc}\n
[1492040] - Refs #201: Added license header that was missing from new file
in [1492038], fixed a truncated license header and moved license headers
to top of template files to normalize position across all templates.
}}}
Differences between these two testing environments are documented in the
docstrings of `BloodhoundFunctionalTester` class.
Disclaimer : This is still work in progress . Major TODOs are :
- Integrate the functional suite smoothly into the multi-product test
suite .
- Write loaders for functional test cases
- Enable test discovery for functional test cases
- Rewrite some test cases after updating Genshi templates to deal with
[http://goo.gl/as0uU nested forms in ticket view] ,
thus prematurely halting twill parser when trying to extract form data
- Deal with package dependencies prior to running Bloodhound installer
script
- Transform current failures into successful test cases (see
[http://goo.gl/FtZhi this spreadsheet])
{{{#!sh
$ python setup.py test -m tests.functional
[...]
---
Ran 126 tests in 892.802s
FAILED (failures=18, errors=18)
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/387#comment:4
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #509: Test compatibility with XMLRPC Plug-in
#509: Test compatibility with XMLRPC Plug-in ---+-- Reporter: mbooth| Owner: mbooth Type: task | Status: review Priority: critical | Milestone: Component: plugins |Version: Resolution:| Keywords: rpc XmlRpcPlugin ---+-- Comment (by olemis): Patches refreshed see comment:4:ticket:387 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/509#comment:14 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #548: Simple ticket report fails
#548: Simple ticket report fails -+- Reporter: olemis | Owner: olemis Type: defect | Status: review Priority: blocker | Milestone: Release 6 Component: |Version: multiproduct | Keywords: sql reports, multiproduct db Resolution: | translator, trac util -+- Comment (by olemis): Replying to [comment:4 rjollos]: (In [1492534]) Refs #548: Account for possibility that template timestamp argument could be a unicode string. --- Reassigning to Olemis for review and final confirmation of whether the issue is fixed. After [1492534] the last query (i.e. `SELECT * FROM ticket`) will work. Nevertheless the former (i.e. `select * from ticket`) still fails . If this expected behavior then feel free to close this ticket as `fixed`. thanks ! -- Ticket URL: https://issues.apache.org/bloodhound/ticket/548#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] Proposals/BEP-0008 modified
Page Proposals/BEP-0008 was changed by huaxiang Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008?action=diffversion=2 Revision 2 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0008 = --- Proposals/BEP-0008 (version: 1) +++ Proposals/BEP-0008 (version: 2) @@ -1,85 +1,64 @@ -placeholder for Hua's proposal- -= BEP BEP number : BEP title #overview += BEP-0008 : Add time series reports #overview [[PageOutline]] -|| '''BEP''' || BEP number || -|| '''Title''' || BEP title || -|| '''Version''' || leave blank || -|| '''Last-Modified''' || leave blank || -|| '''Author''' || Author With Email u...@dom.ain, Author Name Only, or The Bloodhound project (see [wiki:/Proposals#bep-header-preamble BEP preamble explained]) || +|| '''BEP''' || BEP-0008 || +|| '''Title''' || Add time series reports || +|| '''Version''' || || +|| '''Last-Modified''' || || +|| '''Author''' || Hua Xiang huaxiang2...@gmail.com || || '''Status''' || Draft || -|| '''Type''' || BEP type (see [wiki:/Proposals#bep-types BEP types explained]) || +|| '''Type''' || || || '''Content-Type''' || [wiki:PageTemplates/Proposals text/x-trac-wiki] || -|| '''Created''' || leave blank || -|| '''Post-History''' || leave blank || +|| '''Created''' || || +|| '''Post-History''' || || == Abstract #abstract +In many organisations reports are tracking changes over time or and/or are prepared in a regular interval to capture information at a fixed point in time. The current reports functionality of Bloodhound doesn't serve these cases very well at the moment. Users also can't query information as it was at a given date. For solving this problem, the changes over time must be recorded. Data mining tools should also be involved in order to provide some patterns, generate time series reports, help user get better understanding of the reports and make decisions. -Delete text in this section and add a short (~200 word) description of the technical issue being addressed. Take a look at sample abstract below - -This template provides a boilerplate or sample template for creating your -own BEPs. In conjunction with the [wiki:/Proposals general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] -, this should make it easy for you to conform your own -BEPs to the format outlined below. See [#howto How to Use This Template] for further instructions. - -**Note**: if you are reading this template via the web, you should first try to create a new wiki page by selecting `ProposalsRst` |page template guide|. **DO NOT EDIT THIS WIKI PAGE IN ORDER TO CREATE A NEW BEP! ** - -If you would prefer not to use WikiFormatting markup in your BEP, please see [wiki:/Proposals/Formats/RestructuredText reStructuredText BEP guidelines]. == Motivation == -The motivation is critical for BEPs that want to change the copy of ''Trac'' patched using vendor branch . It should clearly explain why the existing ''Bloodhound'' solution is inadequate to address the problem that the ''BEP'' solves. ''BEP'' submissions without sufficient motivation may be rejected outright. +The current “Reports” tool of bloodhound can provide a list based on custom queries (https://issues.apache.org/bloodhound/report). The historical statuses of tickets and the time point of such information, however, cannot be illustrated. These data are helpful for user to determine the hottest topics, allocate resources, evaluate performance etc. + == Proposal #proposal -The technical specification should describe any new features , detail its impact on the components architecture , mention what plugins will be included as a result , whether they are hosted by [http://trac-hacks.org trac-hacks.org] or not , and any other relevant technical subject . The specification should be detailed enough to allow competing, interoperable implementations for any of the current supported database platforms (e.g. ''SQLite'', ''Postgres'', ''MySQL'') and server technologies (e.g. ''Apache HTTPD server'', ''nginx'', ''mod_wsgi'', ''CGI'').. +To help the Bloodhound developers find the hidden information easily and make correct decisions. For example, for a particular type of tickets, the longer the time of changing status from 'assigned' to 'closed', the higher the difficulty level of solving. Therefore, the developers can allocate more resources for such type of tickets. -== Rationale #rationale +To help users to track the process of their own tickets, e.g., a message/email sent to the user once the status of the ticket was changed. -The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other issue
