[Apache Bloodhound] New user registration: mudri
New user registration for user mudri -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #271: Monospace font family for text area inputs
#271: Monospace font family for text area inputs
--+-
Reporter: olemis | Owner: nobody
Type: enhancement | Status: new
Priority: trivial | Milestone:
Component: ui design|Version:
Resolution: | Keywords: css starter
--+-
Comment (by mudri):
{{{
#!css
Index: bloodhound_theme/bhtheme/htdocs/bloodhound.css
===
--- bloodhound_theme/bhtheme/htdocs/bloodhound.css (revision 1505634)
+++ bloodhound_theme/bhtheme/htdocs/bloodhound.css (working copy)
@@ -1281,3 +1281,7 @@
input[type=radio]:not(:checked) + label span {
text-decoration:underline;
}
+
+textarea {
+ font-family: monospace;
+}
}}}
This should do.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/271#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #271: Monospace font family for text area inputs
#271: Monospace font family for text area inputs --+- Reporter: olemis | Owner: mudri Type: enhancement | Status: assigned Priority: trivial | Milestone: Component: ui design|Version: Resolution: | Keywords: css starter --+- Changes (by mudri): * owner: nobody = mudri * status: new = assigned -- Ticket URL: https://issues.apache.org/bloodhound/ticket/271#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column product specified more than onceLINE 1: ...tus, product, severity, keywords, cc, time, changetime, product) V... ^
#601: ProgrammingError: column product specified more than onceLINE 1:
...tus,product,severity,keywords,cc,time,changetime, product) V...
^
---+
Reporter: ogaerick | Owner: nobody
Type: defect| Status: new
Priority: blocker | Milestone:
Component: multiproduct |Version: 0.6.0
Resolution:| Keywords:
---+
Comment (by rjollos):
When I create a ticket using the quick ticket form, the following SQL is
executed (`[trac] debug_sql = true`):
{{{
04:32:59 AM Trac[dbcursor] DEBUG: SQL: INSERT INTO ticket
(summary,reporter,owner,description,type,status,priority,product,milestone,component,version,resolution,time,changetime,
product) VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,'prod1')
04:32:59 AM Trac[util] DEBUG: SQL: INSERT INTO ticket
(summary,reporter,owner,description,type,status,priority,product,milestone,component,version,resolution,time,changetime,
product) VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,'prod1')
}}}
The duplication of the `product` field, caused by the addition of the
`product` select in #569, doesn't seem to cause a problem with SQLite, but
I'll attempt to reproduce with PostgreSQL.
I'm not seeing a duplication of the `product` field for tickets created
from the `/newticket` URL (i.e. the full new ticket form):
{{{
03:46:38 AM Trac[dbcursor] DEBUG: Original SQl: INSERT INTO ticket
(summary,reporter,owner,descriobserving this
issueption,type,status,priority,milestone,component,version,keywords,cc,time,changetime)
VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s)
03:46:38 AM Trac[dbcursor] DEBUG: SQL: INSERT INTO ticket
(summary,reporter,owner,description,type,status,priority,milestone,component,version,keywords,cc,time,changetime,
product) VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,'@')
}}}
The latter finding isn't too surprising since there shouldn't be a product
select field within the `#inplace-propertyform` form. The product select
should only exist on the breadcrumb. Do you see a product select field in
the new ticket form when on the `/newticket` page?
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/601#comment:5
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #604: Default Product can't be deactivated
#604: Default Product can't be deactivated ---+ Reporter: ogaerick | Owner: nobody Type: defect| Status: new Priority: critical | Milestone: Component: multiproduct |Version: 0.6.0 Resolution:| Keywords: ---+ Comment (by rjollos): This may effectively be solved by #578. Please see [http://markmail.org/message/xvdfpebypjn43fps this comment] from a mailing list discussion. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/604#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #602: Allow product to be select from the ticket from (was: Product selection)
#602: Allow product to be select from the ticket from ---+ Reporter: ogaerick | Owner: nobody Type: enhancement | Status: new Priority: critical | Milestone: Component: multiproduct |Version: 0.6.0 Resolution:| Keywords: ---+ Comment (by rjollos): I assume that you mean //new ticket// form. The quick create ticket form has a //product// field by default, but you may have configured `[ticket] quick_create_fields` and removed it. The //new ticket// form will create a ticket for the product in the current scope. The scope can be changed using the select on the breadcrumb, but this is inconvenient, and we should make it easier to change the product when creating a new ticket. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/602#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #602: Allow product to be selected from the new ticket from (was: Allow product to be select from the ticket from)
#602: Allow product to be selected from the new ticket from ---+ Reporter: ogaerick | Owner: nobody Type: enhancement | Status: new Priority: critical | Milestone: Component: multiproduct |Version: 0.6.0 Resolution:| Keywords: ---+ -- Ticket URL: https://issues.apache.org/bloodhound/ticket/602#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column product specified more than onceLINE 1: ...tus, product, severity, keywords, cc, time, changetime, product) V... ^
#601: ProgrammingError: column product specified more than onceLINE 1: ...tus,product,severity,keywords,cc,time,changetime, product) V... ^ ---+ Reporter: ogaerick | Owner: nobody Type: defect| Status: new Priority: blocker | Milestone: Component: multiproduct |Version: 0.6.0 Resolution:| Keywords: ---+ Comment (by astaric): I have managed to replicate the qct problem it in postgres and commited a fix in r1505666. It fixes the issue for me. ogaerick, can you try the trunk version of bloodhound and see, if you still get the same error? -- Ticket URL: https://issues.apache.org/bloodhound/ticket/601#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #271: Monospace font family for text area inputs
#271: Monospace font family for text area inputs
--+-
Reporter: olemis | Owner: mudri
Type: enhancement | Status: assigned
Priority: trivial | Milestone:
Component: ui design|Version:
Resolution: | Keywords: css starter
--+-
Comment (by mudri):
{{{
#!css
Index: bloodhound_theme/bhtheme/htdocs/bloodhound.css
===
--- bloodhound_theme/bhtheme/htdocs/bloodhound.css (revision 1505634)
+++ bloodhound_theme/bhtheme/htdocs/bloodhound.css (working copy)
@@ -1281,3 +1281,8 @@
input[type=radio]:not(:checked) + label span {
text-decoration:underline;
}
+
+#content textarea,
+.popover-content textarea {
+ font-family: monospace;
+}
}}}
Slightly better. Targets description, comments and wiki editors only.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/271#comment:4
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column product specified more than onceLINE 1: ...tus, product, severity, keywords, cc, time, changetime, product) V... ^
#601: ProgrammingError: column product specified more than onceLINE 1: ...tus,product,severity,keywords,cc,time,changetime, product) V... ^ ---+ Reporter: ogaerick | Owner: nobody Type: defect| Status: new Priority: blocker | Milestone: Component: multiproduct |Version: 0.6.0 Resolution:| Keywords: ---+ Comment (by olemis): Replying to [comment:6 astaric]: I have managed to replicate the qct problem it in postgres and commited a fix in r1505666. It fixes the issue for me. ogaerick, can you try the trunk version of bloodhound and see, if you still get the same error? I'm still getting the same error in PostgreSQL using both /qct and /newticket in product context . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/601#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #601: ProgrammingError: column product specified more than onceLINE 1: ...tus, product, severity, keywords, cc, time, changetime, product) V... ^
#601: ProgrammingError: column product specified more than onceLINE 1: ...tus,product,severity,keywords,cc,time,changetime, product) V... ^ ---+ Reporter: ogaerick | Owner: nobody Type: defect| Status: new Priority: blocker | Milestone: Component: multiproduct |Version: 0.6.0 Resolution:| Keywords: ---+ Comment (by olemis): Replying to [comment:7 olemis]: Replying to [comment:6 astaric]: I have managed to replicate the qct problem it in postgres and commited a fix in r1505666. It fixes the issue for me. ogaerick, can you try the trunk version of bloodhound and see, if you still get the same error? I'm still getting the same error in PostgreSQL using both /qct and /newticket in product context . JFTR, it seems there's an `input type=hidden id=field-product name=field_product value=dataviz /` element in `form#propertyform` in /newticket page . Nevertheless, in any case backend code has to be robust so as not to fail. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/601#comment:8 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] New user registration: ProT-0-TypE
New user registration for user ProT-0-TypE -- 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=5 Revision 5 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0008 = --- Proposals/BEP-0008 (version: 4) +++ Proposals/BEP-0008 (version: 5) @@ -29,15 +29,16 @@ 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. -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. - -To help developers and users get better understanding of the reports and make decisions. - Proposed solution: · Take snaps to keep the changes of statuses and the time those occurred. · Use data mining tools to find some patterns, generate time series reports. - == Rationale #rationale + == Progress +* Spot methods/functions can be used to generate time-series report. (Done by early July) +* Create non-graphic time-series reports for a specific query from local host. (Done by mid-term ) +* Add enhanced reports functionality. +* Generate graphic time-series reports. + == Implementation #implementation ---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 .
Re: [Apache Bloodhound] #601: ProgrammingError: column product specified more than onceLINE 1: ...tus, product, severity, keywords, cc, time, changetime, product) V... ^
#601: ProgrammingError: column product specified more than onceLINE 1:
...tus,product,severity,keywords,cc,time,changetime, product) V...
^
---+
Reporter: ogaerick | Owner: nobody
Type: defect| Status: new
Priority: blocker | Milestone:
Component: multiproduct |Version: 0.6.0
Resolution:| Keywords:
---+
Comment (by olemis):
Below I explain the reason why I'm still getting the same error this side
.
Replying to [comment:5 rjollos]:
When I create a ticket using the quick ticket form, the following SQL is
executed (`[trac] debug_sql = true`):
{{{
04:32:59 AM Trac[dbcursor] DEBUG: SQL: INSERT INTO ticket
(summary,reporter,owner,description,type,status,priority,product,milestone,component,version,resolution,time,changetime,
product) VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,'prod1')
04:32:59 AM Trac[util] DEBUG: SQL: INSERT INTO ticket
(summary,reporter,owner,description,type,status,priority,product,milestone,component,version,resolution,time,changetime,
product) VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,'prod1')
}}}
The duplication of the `product` field, caused by the addition of the
`product` select in #569, doesn't seem to cause a problem with SQLite, but
I'll attempt to reproduce with PostgreSQL.
I'm not seeing a duplication of the `product` field for tickets created
from the `/newticket` URL (i.e. the full new ticket form):
{{{
03:46:38 AM Trac[dbcursor] DEBUG: Original SQl: INSERT INTO ticket
(summary,reporter,owner,descriobserving this
issueption,type,status,priority,milestone,component,version,keywords,cc,time,changetime)
VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s)
03:46:38 AM Trac[dbcursor] DEBUG: SQL: INSERT INTO ticket
(summary,reporter,owner,description,type,status,priority,milestone,component,version,keywords,cc,time,changetime,
product) VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,%s,'@')
}}}
Unfortunately `INSERT` statements are not logged in my instance . I can
only see lines for `SELECT` statements . I'd appreciate if you share any
ideas .
The latter finding isn't too surprising since there shouldn't be a
product select field within the `#inplace-propertyform` form. The product
select should only exist on the breadcrumb. Do you see a product select
field in the new ticket form when on the `/newticket` page?
As far as I can tell it always inserts product field twice my side . I
reproduced the sequence of invocations leading to the error in
`trac.ticket.model.Ticket` and this is what I get
{{{#!py
from trac.env import open_environment as oe
genv = oe('/path/to/blood-hound.net')
from multiproduct.env import ProductEnvironment as PE
penv = PE(genv, 'dataviz')
from multiproduct.dbcursor import translate_sql
# Headless test mode ;)
sql = translate_sql(penv, INSERT INTO ticket (summary, product)
VALUES ('S', 'swlcu'))
sql
uINSERT INTO ticket (summary, product, product) VALUES ('S',
'swlcu','dataviz')
from trac.ticket.model import Ticket
t = Ticket(penv)
self = t
# Copy and paste lines 226-235 in trac/ticket/model.py
if True:
... std_fields = []
... custom_fields = []
... for f in self.fields:
... fname = f['name']
... if fname in self.values:
... if f.get('custom'):
... custom_fields.append(fname)
... else:
... std_fields.append(fname)
...
# The query in lines 238-241
orig = (INSERT INTO ticket (%s) VALUES (%s)
...% (','.join(std_fields),
... ','.join(['%s'] * len(std_fields
orig
'INSERT INTO ticket (owner,type,priority,product,version) VALUES
(%s,%s,%s,%s,%s)'
sql = translate_sql(penv, orig)
sql
uINSERT INTO ticket (owner,type,priority,product,version, product) VALUES
(%s,%s,%s,%s,%s,'dataviz')
}}}
`product` appears twice because
1. it is included in `std_fields` via ITicketFieldsProvider
2. and appended once again after translation
All this happens using PostgreSQL backend .
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/601#comment:9
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
[Apache Bloodhound] #605: ☆ BEP-0008 #2 Display historical status changes for all ticket
#605: ☆ BEP-0008 #2 Display historical status changes for all ticket ---+--- Reporter: huaxiang |Owner: Type: defect| Status: new Priority: major | Version: Resolution:| ---+--- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/605 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #605: ☆ BEP-0008 #2 Display historical status changes for all ticket
#605: ☆ BEP-0008 #2 Display historical status changes for all ticket +-- Reporter: huaxiang | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: BEP-0008 +-- Changes (by huaxiang): * keywords: = BEP-0008 * owner: = nobody * component: = dashboard -- Ticket URL: https://issues.apache.org/bloodhound/ticket/605#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #605: ☆ BEP-0008 #2 Display historical status changes for all ticket order by ticket id (was: ☆ BEP-0008 #2 Display historical status changes for all ticket)
#605: ☆ BEP-0008 #2 Display historical status changes for all ticket order by ticket id +-- Reporter: huaxiang | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: BEP-0008 +-- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/605#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] #606: BEP-0008 #3 Display ticket info given a ticket id and time range
#606: BEP-0008 #3 Display ticket info given a ticket id and time range ---+--- Reporter: huaxiang |Owner: Type: defect| Status: new Priority: major | Version: Resolution:| ---+--- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/606 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #605: ☆ BEP-0008 #2 Display historical status changes for all ticket order by ticket id
#605: ☆ BEP-0008 #2 Display historical status changes for all ticket order by ticket id +-- Reporter: huaxiang | Owner: nobody Type: task | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: BEP-0008 +-- Changes (by huaxiang): * type: defect = task -- Ticket URL: https://issues.apache.org/bloodhound/ticket/605#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #606: BEP-0008 #3 Display ticket info given a ticket id and time range
#606: BEP-0008 #3 Display ticket info given a ticket id and time range +-- Reporter: huaxiang | Owner: nobody Type: task | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: BEP-0008 +-- Changes (by huaxiang): * keywords: = BEP-0008 * owner: = nobody * component: = dashboard * type: defect = task -- Ticket URL: https://issues.apache.org/bloodhound/ticket/606#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
svn commit: r1505871 - in /bloodhound/trunk: bloodhound_dashboard/bhdashboard/widgets/templates/ bloodhound_multiproduct/multiproduct/ bloodhound_theme/bhtheme/templates/ trac/trac/ticket/
Author: rjollos
Date: Tue Jul 23 00:53:51 2013
New Revision: 1505871
URL: http://svn.apache.org/r1505871
Log:
Reverse merge [1505863].
Modified:
bloodhound/trunk/bloodhound_dashboard/bhdashboard/widgets/templates/widget_grid.html
bloodhound/trunk/bloodhound_multiproduct/multiproduct/dbcursor.py
bloodhound/trunk/bloodhound_theme/bhtheme/templates/bh_report_view.html
bloodhound/trunk/trac/trac/ticket/api.py
bloodhound/trunk/trac/trac/ticket/model.py
bloodhound/trunk/trac/trac/ticket/report.py
Modified:
bloodhound/trunk/bloodhound_dashboard/bhdashboard/widgets/templates/widget_grid.html
URL:
http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_dashboard/bhdashboard/widgets/templates/widget_grid.html?rev=1505871r1=1505870r2=1505871view=diff
==
---
bloodhound/trunk/bloodhound_dashboard/bhdashboard/widgets/templates/widget_grid.html
(original)
+++
bloodhound/trunk/bloodhound_dashboard/bhdashboard/widgets/templates/widget_grid.html
Tue Jul 23 00:53:51 2013
@@ -61,7 +61,7 @@
}${'__style__' in row and row.__style__+';' or None
}${fullrow and 'border: none; padding: 0;' or None}
- td py:if=use_groups py:choose=
+ td py:if=use_groups py:choose=
style=background: none repeat scroll 0 0 #FF; color:
#33;
py:when test=idx == 0 and value_for_group and not fullrow
$value_for_group
@@ -75,33 +75,33 @@
py:if test=not cell.header.hidden
py:with vars=col = cell.header.col.strip('_')
py:choose
-
+
!--! for the report listing --
py:when test=col == 'report'
td class=$col py:attrs=td_attrs
a title=View report
href=${href.report(cell.value)}{$cell.value}/a
/td
/py:when
-
+
py:when test=col == 'title'
td class=$col py:attrs=td_attrs
a title=View report
href=${href.report(row.id)}$cell.value/a
/td
/py:when
-
+
!--! for the ticket listing --
py:when test=col in ('ticket', 'id')
td class=ticket py:attrs=td_attrs
a title=View ${row.resource.realm}
href=${row.href if row.href else
url_of(row.resource)}${shortname_of(row.resource)}/a
/td
/py:when
-
+
py:when test=col == 'summary' and row.id
td class=$col py:attrs=td_attrs
a title=View ${row.resource.realm}
href=${row.href if row.href else url_of(row.resource)}$cell.value/a
/td
/py:when
-
+
!--! generic fields --
py:when test=col == 'time' py:with=value =
int(cell.value) if isinstance(cell.value, basestring) else cell.value
td class=date py:attrs=td_attrs${cell.value !=
'' and format_time(value) or '--'}
@@ -113,7 +113,7 @@
/td
/py:when
- py:when test=col in ('datetime','tctime')
py:with=value = int(cell.value) if isinstance(cell.value, basestring) else
cell.value
+ py:when test=col == 'datetime' py:with=value =
int(cell.value) if isinstance(cell.value, basestring) else cell.value
td class=date py:attrs=td_attrs${cell.value !=
'' and format_datetime(value) or '--'}
/td
/py:when
@@ -123,18 +123,18 @@
${wiki_to_html(context(row.resource), cell.value)}
/td
/py:when
-
+
py:when test=col == 'milestone'
td class=$col py:attrs=td_attrs
a title=View milestone
href=${href.milestone(cell.value)}$cell.value/a
/td
/py:when
-
+
py:otherwise
td class=$col py:attrs=td_attrs$cell.value
/td
/py:otherwise
-
+
/py:choose
/py:with
/py:if
Modified: bloodhound/trunk/bloodhound_multiproduct/multiproduct/dbcursor.py
URL:
http://svn.apache.org/viewvc/bloodhound/trunk/bloodhound_multiproduct/multiproduct/dbcursor.py?rev=1505871r1=1505870r2=1505871view=diff
==
--- bloodhound/trunk/bloodhound_multiproduct/multiproduct/dbcursor.py (original)
+++ bloodhound/trunk/bloodhound_multiproduct/multiproduct/dbcursor.py Tue
Re: [Apache Bloodhound] #607: BEP-0008 #3 Calculate and display average time to finish tasks
#607: BEP-0008 #3 Calculate and display average time to finish tasks +-- Reporter: huaxiang | Owner: nobody Type: task | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: BEP-0008 +-- Changes (by huaxiang): * owner: = nobody * component: = dashboard * type: defect = task * keywords: = BEP-0008 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/607#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] New user registration: aclave1
New user registration for user aclave1 -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] BloodhoundInstall modified
Page BloodhoundInstall was changed by aclave1
Diff URL:
https://issues.apache.org/bloodhound/wiki/BloodhoundInstall?action=diffversion=21
Revision 21
Changes:
---8--8--8--8--8--8--8--8
Index: BloodhoundInstall
=
--- BloodhoundInstall (version: 20)
+++ BloodhoundInstall (version: 21)
@@ -149,7 +149,7 @@
== Web Server ==
-If you have managed to prove that you can run the system with the standalone
tracd, you should now also be able to run through a web server. Here we provide
details about how to use the Apache webserver. It is currently recommended to
use Apache with mod_wsgi to serve Bloodhound. The following instructions
require apache to be installed along with the wsgi and auth_digest modules.
+If you have managed to prove that you can run the system with the standalone
tracd, you should now also be able to run through a web server. Here we provide
details about how to use the Apache webserver. It is currently recommended to
use Apache with mod_wsgi (libapache2-mod-wsgi) to serve Bloodhound. The
following instructions require apache to be installed along with the wsgi and
auth_digest modules.
It is possible to get the trac-admin command to reduce some of the work of
creating the wsgi file
{{{
@@ -169,7 +169,7 @@
sudo vi /etc/apache2/sites-available/bloodhound
}}}
-Add to this something like:
+Add to this something like (Note that /path/to/bloodhound means
/path/to/apache-bloodhound-incubating-version number/installer/bloodhound) :
{{{
VirtualHost *:8080
WSGIDaemonProcess bh_tracker user=bloodhound
python-path=/path/to/bloodhound/lib/python2.7/site-packages
---8--8--8--8--8--8--8--8
--
Page URL: https://issues.apache.org/bloodhound/wiki/BloodhoundInstall
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 'BloodhoundInstall' page.
If it was not you, please report to .
