Re: [Apache Bloodhound] #554: Last Login does not update
#554: Last Login does not update
---+
Reporter: rjollos | Owner: rjollos
Type: defect| Status: accepted
Priority: critical | Milestone: Release 6
Component: plugins |Version: 0.5.3
Resolution:| Keywords: AccountManager
---+
Comment (by astaric):
I can confirm, that last_visit does not update after each login.
However, both setups (bloodhound and trac) with the login options I tested
(!AccountManager, --auth, --basic-auth) behave in the same way,
last_visit time is only updated when
- session is created for the first time (first login)
- when session data is modified and sufficient amount of time has passed.
Only the first loggin satisfies this requirements and (in every setup I
have tried) creates a session record with last_visit filled in. The
following logins do not automatically modify the last_visit field.
My guess is that last_visit was not ment to be used as Last login time,
but as a helper to decide, when the session data can be removed from the
database. I based my observation on the comment just before the code that
updates the last_visit time.
{{{
# Purge expired sessions. We do this only when the session was
# changed as to minimize the purging.
}}}
As long as the admin panel reads data from Session.last_visit, column
caption Last Login is misleading.
We could touch the session data after each successful login, which would
keep this field (more) up to date, but the real solution would probably be
to store logins in a separate table. If we consider this an important
issue, we could propose a patch to !AccountManager or hack around to
manually update the last_visit time.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/554#comment:17
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #541: TracStandalone crashing on default product misconfiguration
#541: TracStandalone crashing on default product misconfiguration ---+- Reporter: olemis| Owner: rjollos Type: defect| Status: review Priority: critical | Milestone: Component: multiproduct |Version: Resolution:| Keywords: hooks ---+- Comment (by olemis): Replying to [comment:9 rjollos]: Replying to [comment:8 olemis]: Replying to [comment:7 rjollos]: I've also tried with `[multiproduct] `default_product_prefix` set to a non-existent product, but can't reproduce still. You won't because the system you are testing against is different to the one I used once I reported the issue . Like [comment:11:ticket:561 I mentioned before] the patches for #561 (already committed?) are related to this issue as well . Just go back to a changeset prior to those modifications and you'll notice . Let me ask just to be sure. You are saying if I go back to the revision prior to that which the patches for #561 were committed, then I can reproduce the issue by setting `[multiproduct] default_product_prefix` to a non-existent product? At least [comment:1 when I reported this ticket] that's what was happening to me. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/541#comment:10 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] #572: Apply permission checks to default Dashboard widgets
#572: Apply permission checks to default Dashboard widgets ---+ Reporter: astaric| Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: Keywords: | ---+ Global Dashboard currently displays widgets that display product data, but do not check product specific permissions. If user has TICKET_VIEW permission in global context, he can see unfiltered lists of products and product tickets. The following steps can be used to reproduce the problems: Create two products with some tickets (DEMO and MNP). Grant anonymous *_VIEW on global, but no product specific permissions. With this setup, anonymous can access global Dashboard, where it sees all the tickets and all the products. He cannot access product specific dashboards (no PRODUCT_VIEW permission). Links to products/tickets in the global dashboard also redirect to login. If anonymous is grantet additional PRODUCT_VIEW permission for both products, he can access the dashboards, but ticket and timeline widgets crash (no TICKET_VIEW permissions). trac:TracFineGrainedPermissions should also be included in permission check. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/572 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #541: TracStandalone crashing on default product misconfiguration
#541: TracStandalone crashing on default product misconfiguration ---+- Reporter: olemis| Owner: rjollos Type: defect| Status: review Priority: critical | Milestone: Component: multiproduct |Version: Resolution:| Keywords: hooks ---+- Comment (by olemis): After checking out r1494718 I get `TracError: LookupError: Missing product x` message but TracStandalone server does not crash. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/541#comment:11 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #569: QCT view/edit link can direct to Error: Invalid ticket number
#569: QCT view/edit link can direct to Error: Invalid ticket number ---+ Reporter: rjollos | Owner: nobody Type: defect| Status: new Priority: major | Milestone: Component: multiproduct |Version: Resolution:| Keywords: ---+ Comment (by matevzb): Replying to [comment:1 rjollos]: When in the scope of a product, I think that tickets should be created for that product. I know this was discussed on the mailing list. Am I remember correctly the intended behavior? That was the intended behaviour, and it seems to work this way unless default_product is set in the configuration. What Joe recommends also makes sense, so that one can quick-create a ticket for other products even when not in that scope. If I understand correctly, QCT should default to the product in the current scope, but still allow selection of other products. And when invoked in the global scope, it should default to the default_product. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/569#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] Deleted User: nokia6
Deleted User for user nokia6 -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #571: nokia 6
#571: nokia 6 + Reporter: nokia6 | Owner: Type: task | Status: closed Priority: major | Milestone: Component: dashboard |Version: 0.3.0 Resolution: invalid| Keywords: + Changes (by gjm): * status: new = closed * resolution: = invalid * component: = dashboard Old description: a href=http://sieumuachung.vn/;mua chung/a New description: Description removed as this was assumed to be spam. -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/571#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #569: QCT view/edit link can direct to Error: Invalid ticket number
#569: QCT view/edit link can direct to Error: Invalid ticket number ---+ Reporter: rjollos | Owner: nobody Type: defect| Status: new Priority: major | Milestone: Component: multiproduct |Version: Resolution:| Keywords: ---+ Comment (by rjollos): Replying to [comment:5 matevzb]: If I understand correctly, QCT should default to the product in the current scope, but still allow selection of other products. And when invoked in the global scope, it should default to the default_product. I feel that what you suggest is the best solution. Therefore, I propose to: 1. Add a **Product** `select` to the QCT. 1. Default the `select` to the product in current scope. 1. At global scope, default the product `select` to `[ticket] default_product`. 1. If `[ticket] default_product` is not set to a valid product, default the product select to the first `option` in the `select` with the products having been ordered sorted. Whereas (4) should protect against the issue in #568, some additional protection may be added in that ticket. I'll wait for feedback today before making these changes. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/569#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #568: New tickets cannot be viewed
#568: New tickets cannot be viewed
+
Reporter: avp| Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: dashboard |Version:
Resolution: | Keywords:
+
Comment (by rjollos):
To fix the issue, make the following edit in trac.ini:
{{{#!ini
[ticket]
default_product = @
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/568#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #568: New tickets cannot be viewed
#568: New tickets cannot be viewed +--- Reporter: avp| Owner: rjollos Type: defect | Status: accepted Priority: blocker| Milestone: Release 6 Component: dashboard |Version: Resolution: | Keywords: qct +--- Changes (by rjollos): * owner: nobody = rjollos * priority: major = blocker * status: new = accepted * keywords: = qct * milestone: = Release 6 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/568#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #569: QCT view/edit link can direct to Error: Invalid ticket number
#569: QCT view/edit link can direct to Error: Invalid ticket number ---+--- Reporter: rjollos | Owner: rjollos Type: defect| Status: accepted Priority: blocker | Milestone: Release 6 Component: multiproduct |Version: Resolution:| Keywords: qct ---+--- Comment (by jdreimann): Replying to [comment:6 rjollos]: I'll wait for feedback today before making these changes. I agree with your suggestions (obviously) :-) -- Ticket URL: https://issues.apache.org/bloodhound/ticket/569#comment:8 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #556: bh-demo2 site should be labeled Latest Release
#556: bh-demo2 site should be labeled Latest Release ---+ Reporter: rjollos | Owner: nobody Type: task | Status: new Priority: minor | Milestone: Component: projectadmin |Version: Resolution:| Keywords: ---+ Comment (by jdreimann): I've attached a vector version of the Logo, which should make this an easier task for anyone that may pick this up before me. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/556#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] PageTemplates/Proposals modified
Page PageTemplates/Proposals was changed by olemis
Diff URL:
https://issues.apache.org/bloodhound/wiki/PageTemplates/Proposals?action=diffversion=5
Revision 5
Comment: Guidelines and template to include tickets list in new BEP
Changes:
---8--8--8--8--8--8--8--8
Index: PageTemplates/Proposals
=
--- PageTemplates/Proposals (version: 4)
+++ PageTemplates/Proposals (version: 5)
@@ -57,7 +57,13 @@
== Reference Implementation #reference-implementation
- The reference implementation **must** be completed before any ''BEP'' is
given status **Final**, but it need not be completed before the ''BEP'' is
accepted. It is better to finish the specification and rationale first and
reach consensus on it before writing code. The final implementation **must**
include test code and documentation appropriate for either the wiki pages in
''Bloodhound'' users guide or an specific wiki page in the
[http://issues.apache.org/bloodhound ​issue tracker] .
+ The reference implementation **must** be completed before any ''BEP'' is
given status **Final**, but it need not be completed before the ''BEP'' is
accepted. It is better to finish the specification and rationale first and
reach consensus on it before writing code. The final implementation **must**
include test code and documentation appropriate for either the wiki pages in
''Bloodhound'' users guide or an specific wiki page in the
[http://issues.apache.org/bloodhound issue tracker] .
+
+In order to list tickets related to a given proposal edit sample text
provided below by including the appropriate **BEP number**. Do not forget to
remove curly braces so that the tickets list will be actually rendered.
+
+{{{
+[[Widget(TicketQuery, query=keywords=~bep-BEP
numbercol=idcol=summarycol=statuscol=prioritycol=milestone, title=BEP
BEP number ticket summary)]]
+}}}
== Resources #resources
---8--8--8--8--8--8--8--8
--
Page URL: https://issues.apache.org/bloodhound/wiki/PageTemplates/Proposals
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 'PageTemplates/Proposals' page.
If it was not you, please report to .
[Apache Bloodhound] PageTemplates/Proposals modified
Page PageTemplates/Proposals was changed by olemis
Diff URL:
https://issues.apache.org/bloodhound/wiki/PageTemplates/Proposals?action=diffversion=6
Revision 6
Comment: Document in BEP template the keywords needed to get ticket listed
Changes:
---8--8--8--8--8--8--8--8
Index: PageTemplates/Proposals
=
--- PageTemplates/Proposals (version: 5)
+++ PageTemplates/Proposals (version: 6)
@@ -59,7 +59,7 @@
The reference implementation **must** be completed before any ''BEP'' is
given status **Final**, but it need not be completed before the ''BEP'' is
accepted. It is better to finish the specification and rationale first and
reach consensus on it before writing code. The final implementation **must**
include test code and documentation appropriate for either the wiki pages in
''Bloodhound'' users guide or an specific wiki page in the
[http://issues.apache.org/bloodhound issue tracker] .
-In order to list tickets related to a given proposal edit sample text
provided below by including the appropriate **BEP number**. Do not forget to
remove curly braces so that the tickets list will be actually rendered.
+In order to list tickets related to a given proposal edit sample text
provided below by including the appropriate **BEP number**. Target tickets
have to be tagged with `bep-BEP number` keyword. Do not forget to remove
curly braces so that the tickets list will be actually rendered.
{{{
[[Widget(TicketQuery, query=keywords=~bep-BEP
numbercol=idcol=summarycol=statuscol=prioritycol=milestone, title=BEP
BEP number ticket summary)]]
---8--8--8--8--8--8--8--8
--
Page URL: https://issues.apache.org/bloodhound/wiki/PageTemplates/Proposals
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 'PageTemplates/Proposals' page.
If it was not you, please report to .
