Report: Unfinished issues where Peter hasn't had the last word

All reports
# Issues: 84 (3 issues filtered out or hidden)       Next 20 >
Creation dateAscending order Sections Submitted by Urgency Type

Open

I am having trouble with an intermittent site error message. The error goes away when I restart zope, and it have even gone away when I go to another page or in another browser. I can't seem to reproduce it, other than leaving the window open for a while and coming back to it and clicking on any link.

I am working from svn, updated just today to rev300 I think? I am running the cookiecrumbler addin. I have 2 ITPs running under the one root, the first is helpdesk, the second is bbbs. The latter is an addin of the former (so I can see tickets on both from the helpdesk one).

Below is the error message and below that my zope info. Let me know what logs you need.:

 Site Error
An error was encountered while publishing this resource.
KeyError
Sorry, a site error occurred.
Traceback (innermost last):
    * Module ZPublisher.Publish, line 202, in publish_module_standard
    * Module ZPublisher.Publish, line 150, in publish
    * Module Zope2.App.startup, line 221, in zpublisher_exception_hook
    * Module ZPublisher.Publish, line 119, in publish
    * Module ZPublisher.mapply, line 88, in mapply
    * Module ZPublisher.Publish, line 42, in call_object
    * Module Shared.DC.Scripts.Bindings, line 313, in __call__
    * Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
    * Module Products.CheckoutableTemplates.CTFiles, line 336, in _exec
    * Module Products.PageTemplates.PageTemplateFile, line 129, in _exec
    * Module Products.PageTemplates.PageTemplate, line 89, in pt_render
    * Module zope.pagetemplate.pagetemplate, line 117, in pt_render
    * Module zope.tal.talinterpreter, line 271, in __call__
    * Module zope.tal.talinterpreter, line 346, in interpret
    * Module zope.tal.talinterpreter, line 891, in do_useMacro
    * Module zope.tal.talinterpreter, line 346, in interpret
    * Module zope.tal.talinterpreter, line 536, in do_optTag_tal
    * Module zope.tal.talinterpreter, line 521, in do_optTag
    * Module zope.tal.talinterpreter, line 516, in no_tag
    * Module zope.tal.talinterpreter, line 346, in interpret
    * Module zope.tal.talinterpreter, line 534, in do_optTag_tal
    * Module zope.tal.talinterpreter, line 516, in no_tag
    * Module zope.tal.talinterpreter, line 346, in interpret
    * Module zope.tal.talinterpreter, line 623, in do_insertText_tal
    * Module Products.PageTemplates.Expressions, line 228, in evaluateText
    * Module zope.tales.tales, line 696, in evaluate
      URL: StandardHeader
      Line 23, Column 0
      Expression: <PathExpr standard:'here/testAutoLogin'>
      Names:
      {'container': <IssueTracker at /bbbs>,
       'context': <IssueTracker at /bbbs>,
       'default': <object object at 0xb7dfd528>,
       'here': <IssueTracker at /bbbs>,
       'loop': {},
       'nothing': None,
       'options': {'args': ()},
       'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0xb707d0ec>,
       'request': <HTTPRequest, URL=http://helpdesk.mydomain.com:81/bbbs/index_html>;,
       'root': <Application at >,
       'template': <_CTPageTemplateFile at /bbbs/index_html>,
       'user': <IssueUser 'jp'>}
    * Module zope.tales.expressions, line 217, in __call__
    * Module Products.PageTemplates.Expressions, line 161, in _eval
    * Module Products.PageTemplates.Expressions, line 123, in render
    * Module Products.IssueTrackerProduct.IssueTracker, line 10912, in testAutoLogin
    * Module Products.IssueTrackerProduct.IssueTracker, line 5282, in set_session
    * Module ZPublisher.HTTPRequest, line 1239, in __getattr__
    * Module ZPublisher.HTTPRequest, line 1188, in get
    * Module Products.Sessions.SessionDataManager, line 95, in getSessionData
    * Module Products.Sessions.SessionDataManager, line 182, in _getSessionDataObject
    * Module Products.Transience.Transience, line 837, in new_or_existing
    * Module Products.Transience.Transience, line 449, in __setitem__
KeyError: 1226370960 (Also, the following error occurred while attempting to render the standard error message, please see the event log for full details: 1226370960)
Troubleshooting Suggestions
    * The URL may be incorrect.
    * The parameters passed to this resource may be incorrect.
    * A resource that this resource relies on may be encountering an error.
For more detailed information about the error, please refer to the error log.
If the error persists please contact the site maintainer. Thank you for your patience. 

And my zope info:

 Zope Version
(Zope 2.10.5-final, python 2.4.5, linux2)
Python Version
2.4.5 (#0002, Jul 31 2008, 18:51:48) [GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)]
System Platform
linux2
SOFTWARE_HOME
/usr/lib/zope2.10/lib/python
ZOPE_HOME
/usr/lib/zope2.10
INSTANCE_HOME
/var/lib/zope2.10/instance/sandbox
CLIENT_HOME
/var/lib/zope2.10/instance/sandbox/var
Network Services
ZServer.HTTPServer.zhttp_server (Port: 81) 

Submitted by: <jptechnical>
Last week Tuesday 02:51
9 days old
Sections: Support
Type: bug report
Urgency: high
Added Issue followup   -   <jptechnical> permanent link

Just an update, it seems like it is cookie or session related. If I get the error message, I can retype the url (go to root) and the page will come up fine. If I click on the same ticket I was viewing it looks fine.

Last week Wednesday 19:57
 
Added Issue followup   -   <jptechnical> permanent link

Update again. As soon as the pop3 connector created a ticket or an update I got the site error. It affects both IT instances, but the actual zope instance is unaffected. Any ideas?

Last week Friday 22:02
 

 

Open

An error occured when I tried to preview a issue, because the Alias of Notifyable have a non ASCII character. There is any solution? Thanks, Manuel


--------------------------------------------------
Error type: UnicodeDecodeError
Error value: 'ascii' codec can't decode byte 0xf3 in position 6: ordinal not in range(128)

Traceback (innermost last):
Module ZPublisher.Publish, line 119, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 42, in call_object
Module Products.IssueTrackerProduct.IssueTracker, line 11708, in AddIssue
Module Shared.DC.Scripts.Bindings, line 313, in __call__
Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
Module Products.PageTemplates.PageTemplateFile, line 129, in _exec
Module Products.PageTemplates.PageTemplate, line 89, in pt_render
Module zope.pagetemplate.pagetemplate, line 117, in pt_render
Module zope.tal.talinterpreter, line 271, in __call__
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 891, in do_useMacro
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 536, in do_optTag_tal
Module zope.tal.talinterpreter, line 521, in do_optTag
Module zope.tal.talinterpreter, line 516, in no_tag
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 949, in do_defineSlot
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 855, in do_condition
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 534, in do_optTag_tal
Module zope.tal.talinterpreter, line 516, in no_tag
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 745, in do_insertStructure_tal
Module Products.PageTemplates.Expressions, line 221, in evaluateStructure
Module zope.tales.tales, line 696, in evaluate
- URL: AddIssueTemplate
- Line 43, Column 0
- Expression: <PathExpr standard:'here/preview_issue'>
- Names:
{'container': <IssueTracker at /helpdesk>,
'context': <IssueTracker at /helpdesk>,
'default': <object object at 0x2b11e9be5200>,
'here': <IssueTracker at /helpdesk>,
'loop': {},
'nothing': None,
'options': {'args': (<IssueTracker at /helpdesk>,
<HTTPRequest, URL=http://91.121.85.79:9001/helpdesk/AddIssue>;),
'draft_saved': True},
'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x2b11ec173560>,
'request': <HTTPRequest, URL=http://91.121.85.79:9001/helpdesk/AddIssue>;,
'root': <Application at >,
'template': <PageTemplateFile at /helpdesk/AddIssueTemplate>,
'user': <PropertiedUser 'admin'>}
Module zope.tales.expressions, line 217, in __call__
Module Products.PageTemplates.Expressions, line 161, in _eval
Module Products.PageTemplates.Expressions, line 111, in render
Module Products.PageTemplates.ZRPythonExpr, line 79, in call_with_ns
Module Shared.DC.Scripts.Bindings, line 327, in __render_with_namespace__
Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
Module Products.PageTemplates.PageTemplateFile, line 129, in _exec
Module Products.PageTemplates.PageTemplate, line 89, in pt_render
Module zope.pagetemplate.pagetemplate, line 117, in pt_render
Module zope.tal.talinterpreter, line 271, in __call__
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 586, in do_setLocal_tal
Module zope.tales.tales, line 696, in evaluate
- URL: preview_issue
- Line 99, Column 0
- Expression: <PythonExpr here.Always2Notify(format='merged', requireemail=1, include_assignee=1)>
- Names:
{'container': <IssueTracker at /helpdesk>,
'context': <IssueTracker at /helpdesk>,
'default': <object object at 0x2b11e9be5200>,
'here': <IssueTracker at /helpdesk>,
'loop': {},
'nothing': None,
'options': {'args': ()},
'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x2b11ec1889e0>,
'request': <HTTPRequest, URL=http://91.121.85.79:9001/helpdesk/AddIssue>;,
'root': <Application at >,
'template': <PageTemplateFile at /helpdesk/preview_issue>,
'user': <PropertiedUser 'admin'>}
Module Products.PageTemplates.ZRPythonExpr, line 49, in __call__
- __traceback_info__: here.Always2Notify(format='merged', requireemail=1, include_assignee=1)
Module PythonExpr, line 1, in <expression>
Module Products.IssueTrackerProduct.IssueTracker, line 5871, in Always2Notify
Module Products.IssueTrackerProduct.IssueTracker, line 6101, in ShowNameEmail
Module Products.IssueTrackerProduct.Utils, line 445, in html_entity_fixer
UnicodeDecodeError: 'ascii' codec can't decode byte 0xf3 in position 6: ordinal not in range(128)

Submitted by: <Manuel>
Last week Tuesday 02:23
9 days old
Sections: General
Type: bug report
Urgency: normal

 

Open

An error occured when I tried to create a test issue with non ASCII characters. There is any solution? Thanks, Manuel

--------------------------------------------------
Error type: UnicodeDecodeError
Error value: 'ascii' codec can't decode byte 0xf3 in position 6: ordinal not in range(128)

Traceback (innermost last):
Module ZPublisher.Publish, line 119, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 42, in call_object
Module Products.IssueTrackerProduct.IssueTracker, line 11708, in AddIssue
Module Shared.DC.Scripts.Bindings, line 313, in __call__
Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
Module Products.PageTemplates.PageTemplateFile, line 129, in _exec
Module Products.PageTemplates.PageTemplate, line 89, in pt_render
Module zope.pagetemplate.pagetemplate, line 117, in pt_render
Module zope.tal.talinterpreter, line 271, in __call__
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 891, in do_useMacro
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 536, in do_optTag_tal
Module zope.tal.talinterpreter, line 521, in do_optTag
Module zope.tal.talinterpreter, line 516, in no_tag
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 949, in do_defineSlot
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 855, in do_condition
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 534, in do_optTag_tal
Module zope.tal.talinterpreter, line 516, in no_tag
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 745, in do_insertStructure_tal
Module Products.PageTemplates.Expressions, line 221, in evaluateStructure
Module zope.tales.tales, line 696, in evaluate
- URL: AddIssueTemplate
- Line 43, Column 0
- Expression: <PathExpr standard:'here/preview_issue'>
- Names:
{'container': <IssueTracker at /helpdesk>,
'context': <IssueTracker at /helpdesk>,
'default': <object object at 0x2b11e9be5200>,
'here': <IssueTracker at /helpdesk>,
'loop': {},
'nothing': None,
'options': {'args': (<IssueTracker at /helpdesk>,
<HTTPRequest, URL=http://91.121.85.79:9001/helpdesk/AddIssue>;),
'draft_saved': True},
'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x2b11f3955e18>,
'request': <HTTPRequest, URL=http://91.121.85.79:9001/helpdesk/AddIssue>;,
'root': <Application at >,
'template': <PageTemplateFile at /helpdesk/AddIssueTemplate>,
'user': <PropertiedUser 'admin'>}
Module zope.tales.expressions, line 217, in __call__
Module Products.PageTemplates.Expressions, line 161, in _eval
Module Products.PageTemplates.Expressions, line 111, in render
Module Products.PageTemplates.ZRPythonExpr, line 79, in call_with_ns
Module Shared.DC.Scripts.Bindings, line 327, in __render_with_namespace__
Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
Module Products.PageTemplates.PageTemplateFile, line 129, in _exec
Module Products.PageTemplates.PageTemplate, line 89, in pt_render
Module zope.pagetemplate.pagetemplate, line 117, in pt_render
Module zope.tal.talinterpreter, line 271, in __call__
Module zope.tal.talinterpreter, line 346, in interpret
Module zope.tal.talinterpreter, line 586, in do_setLocal_tal
Module zope.tales.tales, line 696, in evaluate
- URL: preview_issue
- Line 99, Column 0
- Expression: <PythonExpr here.Always2Notify(format='merged', requireemail=1, include_assignee=1)>
- Names:
{'container': <IssueTracker at /helpdesk>,
'context': <IssueTracker at /helpdesk>,
'default': <object object at 0x2b11e9be5200>,
'here': <IssueTracker at /helpdesk>,
'loop': {},
'nothing': None,
'options': {'args': ()},
'repeat': <Products.PageTemplates.Expressions.SafeMapping object at 0x2b11f396c518>,
'request': <HTTPRequest, URL=http://91.121.85.79:9001/helpdesk/AddIssue>;,
'root': <Application at >,
'template': <PageTemplateFile at /helpdesk/preview_issue>,
'user': <PropertiedUser 'admin'>}
Module Products.PageTemplates.ZRPythonExpr, line 49, in __call__
- __traceback_info__: here.Always2Notify(format='merged', requireemail=1, include_assignee=1)
Module PythonExpr, line 1, in <expression>
Module Products.IssueTrackerProduct.IssueTracker, line 5871, in Always2Notify
Module Products.IssueTrackerProduct.IssueTracker, line 6101, in ShowNameEmail
Module Products.IssueTrackerProduct.Utils, line 445, in html_entity_fixer
UnicodeDecodeError: 'ascii' codec can't decode byte 0xf3 in position 6: ordinal not in range(128)

Submitted by: <Manuel>
Last week Tuesday 02:06
9 days old
Sections: General
Type: bug report
Urgency: normal

 

Open

#0796 Export to CSV  

The CSV export link in the "List Issues" section does not work correctly when using the "do not show" option. For example, when selecting "Hide completed issues", the CSV file contains completed issues only. So it seems the CSV export always applies filters in the "show only" mode

Submitted by: Name and email hidden
07-Nov 2008
13 days old
Sections: User functions
Type: general
Urgency: normal

 

Open

An error occured when I tried to...


--------------------------------------------------
Error type: NoACLAdderError
Error value: No ACL user object found

Traceback (innermost last):
Module ZPublisher.Publish, line 119, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 42, in call_object
Module Products.IssueTrackerProduct.IssueTracker, line 3622, in SubmitIssue
Module Products.IssueTrackerProduct.IssueTracker, line 3776, in createIssueObject
NoACLAdderError: No ACL user object found

Submitted by: <Paul Malinowski>
06-Nov 2008
2 weeks old
Sections: General
Type: bug report
Urgency: normal

 

Open

#0792 1  

An error occured when I tried to...


--------------------------------------------------
Error type: UnicodeEncodeError
Error value: 'latin-1' codec can't encode characters in position 17644-17646: ordinal not in range(256)

Traceback (innermost last):
Module ZPublisher.Publish, line 122, in publish
Module ZServer.HTTPResponse, line 262, in setBody
Module ZPublisher.HTTPResponse, line 324, in setBody
Module ZPublisher.HTTPResponse, line 476, in _encode_unicode
UnicodeEncodeError: 'latin-1' codec can't encode characters in position 17644-17646: ordinal not in range(256)

Submitted by: <1>
03-Nov 2008
2 weeks and 3 days old
Sections: User functions
Type: info
Urgency: low

 

Open

A recent change in IssueTrackerProduct allows to see the history of changes to an issue. However, changes to custom fields that should only be viewable by some roles are displayed to all.

Jack

Submitted by: Jack
17-Oct 2008
1 month and 4 days old
Sections: General
Type: bug report
Urgency: high

 

Open

How can one order the list of assignees by their full name, in the "assign to..." list?

Thanks

Submitted by: No name or email
17-Oct 2008
1 month and 4 days old
Sections: General
Type: general
Urgency: normal

 

Open

#0787 error  

An error occured when I tried to...Update everything.
Same error when trying to add filter for 1 person, other it works.

--------------------------------------------------
Error type: UnicodeDecodeError
Error value: 'ascii' codec can't decode byte 0xef in position 10: ordinal not in range(128)

<p>Traceback (innermost last):
<ul>

<li> Module ZPublisher.Publish, line 101, in publish</li>

<li> Module ZPublisher.mapply, line 88, in mapply</li>

<li> Module ZPublisher.Publish, line 39, in call_object</li>

<li> Module Products.IssueTrackerProduct.IssueTracker, line 1779, in UpdateEverything</li>

<li> Module Products.IssueTrackerProduct.IssueTracker, line 5564, in UpdateFilterValuerCatalog</li>

<li> Module Products.IssueTrackerProduct.IssueTracker, line 13113, in index_object</li>

<li> Module Products.ZCatalog.ZCatalog, line 528, in catalog_object</li>

<li> Module Products.ZCatalog.Catalog, line 381, in catalogObject</li>

<li> Module Products.PluginIndexes.common.UnIndex, line 252, in index_object</li>

<li> Module Products.PluginIndexes.common.UnIndex, line 282, in _index_object</li>

<li> Module Products.PluginIndexes.common.UnIndex, line 229, in insertForwardIndexEntry</li>

</ul>UnicodeDecodeError: 'ascii' codec can't decode byte 0xef in position 10: ordinal not in range(128)
</p>

Submitted by: <Marcus Elmang>
17-Oct 2008
1 month and 4 days old
Sections: User functions, Filter function
Type: bug report
Urgency: normal
Added Issue followup   -   Jack permanent link

Based on similar issues reported in this tracker (you can use the search function with part of the error message, such as "'ascii' codec can't decode byte"), it seems that you may have to look into which version of Zope you're using and change accordingly. Mine is 2.10.5-final, I think 2.11 works too.

Jack

17-Oct 2008
 
Added Issue followup   -   <Peter Bengtsson> permanent link

What version of Zope and what version of IssueTrackerProduct?

20-Oct 2008
 
Added Issue followup   -   <Marcus Elmang> permanent link

>You're currently using the latest version.
Your installed version: 0.10.2

Zope Version

(Zope 2.7.8-final, python 2.3.5, win32)
Python Version

2.3.5 (#0062, Feb 8 2005, 16:23:02) [MSC v.1200 32 bit (Intel)]
System Platform

win32

20-Oct 2008
 

 

Open

Hi it's me again...

I'm trying to "un-assign" an issue, but I can't find a way to do this. There are some cases where you take an issue, thinking you can resolve it, and if after a while you can't find a way to do it, there is no way to release it back to the common queue, unless you know who to assign it to. In bigger teams, you don't always know who knows what, and if the team is virtual (i.e. not in the same work area), it's hard to get to everybody asking if you can assign it to them... This is a very pratical case, I encounter this issue all the time in my team.

Is there a way to un-assign the issues? Or is it yet again another feature request... (sorry). If you end up doing it, it would be nice if the history could be kept even after un-assigning the issue.

Thanks and keep up the good work!

Jack

Submitted by: Jack
16-Oct 2008
1 month and 5 days old
Sections: User functions
Type: general
Urgency: normal
Added Issue followup   -   <Peter Bengtsson> permanent link

I doubt a quick fix is possible. An issue is considered assigned if there is an assignment object. Who it points to is a different matter. To unassign an issue you'd have to delete the assignment or mark it as void. Neither options exists but that would probably be the right direction to go to get this to happen.

16-Oct 2008
 
Added Issue followup   -   Jack permanent link

Maybe it's doable if you create a new special assignment object at the end of the list of assignment objects when one selects "Unassign" in the list of assignee. This way you keep the fundamental algorythm and you even get to record the full history, including of when the issue was unassigned. What I mean by special assigned object is an additional flag in the assignment object that would be True, or maybe the name variable is None, or whatever.

16-Oct 2008
 

 

Open

#0777 Add Test Issue  

An error occured when I tried to... add a test issue. There actually is an acl_user (LDAPUserFolder) object in the acquisition path. Maybe this Issue Tracker version does not work w/ LDAP User Folder? Or Am I doing something the wrong way?

--------------------------------------------------
Error type: NoACLAdderError
Error value: No ACL user object found

Traceback (innermost last):
Module ZPublisher.Publish, line 115, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 41, in call_object
Module Products.IssueTrackerProduct.IssueTracker, line 3622, in SubmitIssue
Module Products.IssueTrackerProduct.IssueTracker, line 3776, in createIssueObject
NoACLAdderError: No ACL user object found

Submitted by: <Michael>
01-Oct 2008
1 month and 2 weeks and 6 days old
Sections: General
Type: bug report
Urgency: normal

 

Open

I want to add a new role of issuetracker users who have the ability to view, add, edit, take, etc. issues but not delete them. Is this possible? They currently have permission to view and add issues, but the bar with buttons allowing them to "Take, Put On Hold, Reject..." doesn't appear. Is there a specific permission that I've neglected to give them that turns this on?

Thanks in advance!

Submitted by: <Eric Hudson>
15-Aug 2008
3 months and 1 week old
Sections: General
Type: general
Urgency: normal

 

Open

An error occured when I tried to...

Submit first issue




--------------------------------------------------
Error type: NoACLAdderError
Error value: No ACL user object found

Traceback (innermost last):
Module ZPublisher.Publish, line 119, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 42, in call_object
Module Products.IssueTrackerProduct.IssueTracker, line 3622, in SubmitIssue
Module Products.IssueTrackerProduct.IssueTracker, line 3776, in createIssueObject
NoACLAdderError: No ACL user object found

Submitted by: <Sean Duffy>
14-Aug 2008
3 months and 8 days old
Sections: Installation
Type: bug report
Urgency: high
Added Issue followup   -   <Peter Bengtsson> permanent link

Don't install the issuetracker inside a Plone instance. It's a known bug that I need to find time to work on.

15-Aug 2008
 
Added Issue followup   -   <Sean Duffy> permanent link

I installed in the Zope instance created with Plone Unified Installer, but not in a Plone instance. When I ran the unit tests directly from the Zope instance there were no errors.

I added IssueTracker from the Zope 'Add' box and without ever starting the Plone site from within Zope.

If you are willing, and can share with me any clues, I'd be willing to give this some time. Otherwise I'll need to move on.

15-Aug 2008
 

 

Open

Hey I have a suggestion for Issue Tracker.. Wouldn't it be nice to have the change issue form behave the same as the "take", "complete", etc... buttons? When someone changes an issue, it would add a followup message with a summary of the changes. This way, we can keep track of that. What do you think?

Submitted by: Stephen K
16-Jun 2008
5 months and 1 week old
Sections: General
Type: feature request
Urgency: normal
Added Issue followup   -   <atogmalroyamy> permanent link

- Next, rinse the pot cool for 15 to 20 minutes. <a href=http://joltykbboshw.150m.com/bunn/clean-co...-maker-mold.html>clean coffee maker mold</a> <a href=http://joltykbboshw.150m.com/bunn/bunn-model-b8-parts.html>bunn model b8 parts</a>

30-Jul 2008
 

 

Open

At this time, the Issue Tracker User Folder enables the admin of a tracker to input both the username and email address of a user. This is extremely handy, obviously. But there are two other options (to my knowledge) that are tied to a user account. These are "Remember used filter persistently" and "Enable 'Your next action issues'".

My feature request is about making these options available for the admin to set, at the same place as username and email! That would be really great.

Thanks.

Submitted by: No name or email
12-Jun 2008
5 months and 11 days old
Sections: User functions
Type: feature request
Urgency: normal
Added Issue followup   -   <Peter Bengtsson> permanent link

The reason they're outside the userfolder is because they work by cookies too if someone is not using the issue userfolder such as an LDAP solution for example.

16-Jun 2008
 
Added Issue followup   -   No name or email permanent link

Isn't this the case of the email address too? How do they differ in the way they are handled? The same design can't be applied to them too?

16-Jun 2008
 
Added Issue followup   -   <Peter Bengtsson> permanent link

Now I understand what's going on. The user folder has functions for remembering these settings but no forms for setting it.

I kind of don't mind because it keeps these advanced features tucked away. It means that people who are power users won't be confronted with the option until they explore all of their options.

Feel free to suggest a patch to add these options to the add and edit screen for users in the issuetracker user folder.

16-Jun 2008
 
Added Issue followup   -   No name or email permanent link

How do I suggest a path? Should I get an SVN account?

16-Jun 2008
 
Added Issue followup   -   Stephen K permanent link

sorry, I mean how do I suggest a PATCH :)

16-Jun 2008
 

 

Open

Is it possible to log into the IssueTracker using Active Directory credentials? I think there are some products our there which allow that, but not sure if it works with IssueTrackerProduct.

Submitted by: No name or email
02-Jun 2008
5 months and 3 weeks old
Sections: Support
Type: general
Urgency: normal
Added Issue followup   -   No name or email permanent link

Just to let you know, I've been able to implement a User Folder called ACASUserFolder as a replacement to the Issue Tracker User Folder. It uses CAS to log the user in, which is exactly what I needed.

However, the problem now is that the added functionnalities of the Issue Tracker User Folder have been lost, as far as being able to set up the user full name and his email address.

How can one regain this ability to set up a user full name and email from within the Zope manage interface, with ACASUserFolder?

I was thinking about extending ACASUserFolder with these fields, but I'm not sure at all how to integrate that with IssueTracker Folder.

Thank you.

11-Jun 2008
 
Added Issue followup   -   No name or email permanent link

I've done it, I extended the ACASUserFolder to handle all features of Issue Tracker User Folders, it works like a charm now. See you...

16-Jun 2008
 

 

Open

I am currently evaluating this product. I liked all the features and the interface.
I need issues to be created using email. We are using exchange server which is IMAP enabled but POP is not enabled. I am wondering whether issue tracker supports IMAP accounts instead of POP accounts. I could not find anything regarding this in the documentation.

If it is possible, could any one guide me in setting up IMAP account and get issues created automatically?

Thanks,
Anuradha

Submitted by: <Anuradha>
14-Apr 2008
7 months and 10 days old
Sections: Notifications
Type: info
Urgency: normal
Added Issue followup   -   <Peter Bengtsson> permanent link

Short answer, IMAP is not supported. Sorry. I don't know how to make it look like POP3 but maybe it's possible.

17-Apr 2008
 
Added Issue followup   -   No name or email permanent link

Thanks for the resposnse Peter.
I will check out whether it is possible to enable POP3 in exchange server.

17-Apr 2008
 

 

Open

Hello,

I think it's a bug. In the user page, I can't seem to expand the list of "Issues followed up on" after it's been hidden.

Thank you.

Submitted by: <NiBar>
29-Feb 2008
8 months and 3 weeks and 4 days old
Sections: Navigation
Type: bug report
Urgency: low
Added Issue followup   -   <Peter Bengtsson> permanent link

I can't reproduce this. Can you try to figure out what happens or what goes wrong? What's the URL you get after you've clicked "[expand list]"?

28-Mar 2008
 
Added Issue followup   -   <Nick Chalk> permanent link

I'm seeing a similar problem with the "Issues assigned to you" section, but not the other two. The destination URL is:
http://tracker.private.jamies.org.uk:9673/...r/User?expand=assignments

Version numbers are:
Debian Etch
Zope 2.9.6-4etch1
IssueTrackerProduct 0.9.3

Client browser is Debian Iceweasel 2.0.0.14 on Debian unstable.

15-May 2008
 

 

Open

For a user-generated-content site, I want to let users add two kinds of issues:

1) Report offensive content;
2) Take-down requests concerning copyright violation, etc.

I thought this how-to might address my "issue" and it does provide one approach.
http://www.issuetrackerproduct.com/Documen...-Tos/stealth-issue-adding

But the email approach doesn't take account of all the properties of a "real" issue object. I would rather let users add real issues to the system, so that different staff members could handle the two issue types.

Second point: I would implement this as a link on every page, something like, "Report this". The link would have a parameter to automatically add the URL to the URL field of the issue. It shouldn't be too hard for me to do this, but maybe you should include this option in this otherwise very complete product! Thanks!

Submitted by: Name and email hidden
18-Feb 2008
9 months and 6 days old
Sections: User functions
Type: feature request
Urgency: normal

 

Open

Can't figure it out. I do have ACL Users objects. Root of Zope has standard ACL Users folder and IssueTracker instance has Issue Tracker User Folder. What gives?
Zope error message and traceback have me guessing. Is this a bug with product or have I done something bad?

Submitted by: <mike>
15-Feb 2008
9 months and 9 days old
Sections: General
Type: bug report
Urgency: normal
Added Issue followup   -   <Peter Bengtsson> permanent link

It's most likely because you've install the issuetracker inside a Plone site and using the Plone authentication. This is currently not supported which I admit is a shame but I haven't had time to fix that yet.

15-Feb 2008
 
Added Issue followup   -   <test> permanent link

i have tried to installed in zope site then also giving me same error.

07-May 2008
 

 

      Next 20 >


 

Recent report runs