Report: Issues where Peter hasn't had the last word
All reports| Creation date |
Sections | Submitted by | Urgency | Type |
#0800 Intermittent Site Error
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)
9 days old
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.
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?
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)
9 days old
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)
9 days old
Perhaps I am just not looking in the right place, but is there a way to add the issue ID or the issue Title to the subject of the outgoing email when a ticket is created? Currently it just says "Your issue has been added".
The big case where this might be an issue is if a user has their email sorted by thread, I found this to be the case in gmail. Then the notification is buried under the thread and they might not notice that the new issue was created. I don't want my clients, who are not the most tech-saavy, to start creating a bunch of tickets or cross posting tickets because of this.
Is it much trouble to add the issue ID or the title, or both to the email subject? This would totally resolve it.
Thanks for all your hard work Peter! It has been a while, but I am back to spending mucho time with ITP. Finally gave my own old busted helpdesk the heave-ho, so I am sure I will be more active in the coming weeks. Great software!!!
11 days old
Ok. if you enable to show ID with title it will now include the issue ID in the subject line.
Perfect, I updated just now and it works great! Thanks peter.
#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
13 days old
#0795 Error adding an issue
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
2 weeks old
#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)
2 weeks and 3 days old
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
1 month and 4 days old
How can one order the list of assignees by their full name, in the "assign to..." list?
Thanks
1 month and 4 days old
#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>
1 month and 4 days old
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
What version of Zope and what version of IssueTrackerProduct?
>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
#0786 "un-assign" issue
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
1 month and 5 days old
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.
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.
OK hopefully this time it's a genuine request... I have a situation where I need to create single select custom fields. Easy. But then, I need to apply filters with multiple entries, so a multiple select field is required in the filters. But at this time, it's not possible to have a single select field in the Add Issue page, and a multiple select field in the filters. They've got to be the same. So my request here is: Is it possible to add an option to IssueTrackerProduct, that would allow one to select if a filter should be single or multiple?
Thanks and best regards,
Jack
1 month and 1 week old
Ah! This has come up before and I just haven't had time to implement and test it. Single selects should work as multiples on the filtering. It shouldn't be too hard. I just need to find the time. Please do keep reminding me. I don't mind.
Just committed a change that solves this problem. Any select custom fields act as multiples on the filter.
That's great! Thanks for the quick speed, it's nice of you. I've tested and it does indeed work!
I think I've found a little bug. I have a few custom fields whose content is manipulated with javascript. Initially they have only 1 item, but the number of items changes on the fly. It works fine in the Add Issue page because no size parameter is generated in the custom fields, and browsers do a good job at limiting the length of the field themselves. But in the filters, you seem to be providing a size parameter based on the number of items hard-coded into the custom field. So in my case it's only 1... Which means that when my javascript updates the field, it doesn't grow and stays 1 line. If I can be so intrusive as to suggest a fix, I would say you should ditch the size parameter in the filters, so that it behaves in the same way as in the Add Issue page. You shouldn't fear the filter page getting too long, the browsers are pretty good at handling that.
Thank you!
Jack
Hello,
I have a feature request. Is it possible to add the ability to choose the default value of a custom field? At this time, it's possible to choose the default value of the Urgency, Sections and Type fields, but I would like to have that same possibility for the custom fields as well.
Thanks and best regards,
Jack
1 month and 1 week old
Arg I found the option right after I submitted the issue. One can add a "value" parameter to a custom field, that's it! Great. Now how about doing it with multiple values?
Yes, if you have a multiple select and you want to pre-select multiple values.. Well I may ask for too much, this is not my #0001 feature request for sure...
Have you tested if it works now?
#0784? Yes it does. But this issue is different, it's about having multiple options of a select field selected by default ("selected" parameter is present for more than one option). ex:
<select id="id_test" name="test:utf-8:ustring" title="Test">
<option value="A" selected>A</option>
<option value="B" selected>B</option>
<option value="C">C</option>
<option value="D">D</option>
</select>
By default?? That's less obvious to do I'm afraid. One solution would be to write some javascript that selects the defaults.
Yes, that's OK anyway, as I said, no big deal, I'm quite happy with your other fix already.
Hello,
I have a problem with the filters under IE7 (Don't know about IE6 as I don't have it). When you go and apply some filters and then submit your selection, and you realize you had it wrong so you bring the filters again so change them, the previous filters are lost (the current filters are not preselected). It works fine under Firefox 3.
It's quite inconvenient when you don't get your filters right on the first try, you have to go back and select them all over again.
Thank for paying attention!
Jack
1 month and 11 days old
Hmm.. Strange. Do you think it has something to do with the page (the template that shows the filter options) being cached?
Yes, the filter options didn't load with prevention of client cache. Fixed in SVN. Do you know how to upgrade?
Yes I do know, thank you for the quick fix!
#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
1 month and 3 weeks old
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!
3 months and 1 week old
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
3 months and 8 days old
Don't install the issuetracker inside a Plone instance. It's a known bug that I need to find time to work on.
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.
Received this error message in the event.log during a Zope start:
2008-07-16T09:49:56 ERROR Application Couldn't install IssueTrackerProduct
Traceback (most recent call last):
File "/usr/local/zope2.7/lib/python/OFS/Application.py", line 758, in install_product
global_dict, global_dict, silly)
File "/usr/local/zope2.7/instance/Products/IssueTrackerProduct/__init__.py", line 183, in ?
from OFS.content_types import guess_content_type
ImportError: No module named content_types
Running:
Python 2.4.5
Zope 2.11.0
IssueTrackerProduct 0.9.3
Change Notifications:
In Zope 2.11 beta 1 (2007/12/29) Changes.txt the following notice -- Removed OFS.content_types (deprecated since Zope 2.9).
In Zope 2.10.0 beta 1 (2006/05/30) Changes.txt the following notice -- deprecated OFS.content_types (to be removed in Zope 2.11) and replaced all occurences with zope.app.content_types
Solution:
Modified __init__.py line 183 in IssueTrackerProduct directory from OFS.content_types import guess_content_type
to
from zope.app.content_types import guess_content_type
IssueTrackerProduct appears to install and run properly now.
I did a search on this topic but did not find anything. If already reported please accept my apology.
4 months and 1 week old
Thank's a lot Pat. It's been fixed and checked in. Sadly it still complains but that seems to be a bug in Zope 2.11 that we can't do anything about.
Thank you, Peter, for creating a very nice product.
Question: I would like to add several more items, simiilar to Section(s) to the 'Add Issue' and 'Add Quick Issue' screens, e.g. Product, Category, Defect Type. Do you have any other existing templates or examples that might help in doing this? Should I open this as a separate issue? Thanks.
It's going to please you that exactly that was released a few days ago. I would love for you to try it and if it works out for you if you could share a testimonial about using the feature
http://www.issuetrackerproduct.com/News/0.10.1 (scroll to the bottom)
OK, I will try it out and let you know. Thanks!
Hi Peter, Thanks for the reminder. I posted a testimonial about the product. I liked the upgrade process from 0.9.3 to 0.10.1. It was straight forward and easy to do. So far, I am pleased with the tool and our site is using it to record and track customer service calls.
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?
5 months and 1 week old
- 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>
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.
5 months and 11 days old
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.
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?
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.
How do I suggest a path? Should I get an SVN account?
sorry, I mean how do I suggest a PATCH :)