List Issues
Creation date |
Sections | Submitted by | Urgency | Type |
In the Properties/advanced tab I created statuses with initial uppercase words like this...
Submitted, submit
Partially implemented, implementing
Completed, completed
Obsoleted, make obsolete
Waiting info, request more info
Nothing seemed to be adversely affected except for the statistics. In this case the Issue Status graph is OK, but the Issues by Sections graph is broken.
If I change the statuses to be lower case, now the opposite is occurring and there doesn't seem to be a way to make it all work now.
1 month and 3 weeks and 6 days old
Hi,
Ive been using IssueTrackerProduct at school and we have a requirement to use multiple instance across different timezones. However , when I set it up I noticed that all instances pick up the timezone of the "server". Is this right ? Is IssueTrackerProduct capable of handling multiple timezones. Could this be added to the "Properties" section?
Thanks for any possible help. This is a testament to the greatness of open-source!
/\ \/
5 months and 4 days old
Do not work with Zope2 2.12.3 <http://pypi.python.org/pypi/Zope2/2.12.3>;
Textindex error by creation.
Are there simple way to replace Textindexes? I would use TextIndexNG for all.
5 months and 3 weeks and 4 days old
If you follow the link to create a "Root" notifyable from Stage: 7 of 12 in .../manage_PropertiesWizard then you land here:
Issue Tracker Notifyable Container at /manage_addProduct/IssueTrackerProduct
You can't add notifyables there (causes a traceback).
You have to go to:
Issue Tracker Notifyable Container at /global_notifyables
6 months and 3 days old
#0895 Using Zope 2.12.3
StructuredText and WriteLockInterface are not part of the Zope 2.12 distribution. I used easy_install for StructuredText. However, WriteLockInterface is not part of webdav anymore. I found it in 2.11.6, but not in 2.12.
7 months and 3 days old
From http://pypi.python.org/pypi/StructuredText/2.11.1:
StructuredText 2.11.1
WARNING! The 'StructuredText' package has been deprecated and will be removed in Zope 2.12. Use 'zope.structuredtext' instead.
Thanks a lot Suresh for your patch for 2.12. I'm looking forward to have time to do it. I have been doing some work recently on the IssueTrackerProduct but it's been around UI related stuff which I hope will be appreciated.
#0892 install
I installed Zope 2.11.4 ...when I go to extract the issuetracker files I've downloaded there is no simple path Zope/Products ...there is Zope/lib/products ...Zope/skel/products....where exactly do I extract the files?
8 months and 1 day old
I'm not sure actually. Check in the docs/INSTALL.txt file to see if there's anything about that there.
I have a tracker in /sites/tracker
I'm adding some more trackers, and I don't want to add the same user in each, so I added a user folder: /sites/acl_users
I added a Manager user in there.
The default user folder has always been at /acl_users but this doesn't seem to get in the way.
However now when adding a new tracker at /sites/newtracker the wizard does not offer to create a user folder, apparently satisfied with the one at /sites/acl_users
That one is not an issue tracker user folder, so users don't have issue tracker roles or full name.
I think that issue tracker should offer to create an issue tracker user folder if it doesn't find one.
10 months and 8 days old
An error occured when I tried to...
--------------------------------------------------
Error type: UnicodeDecodeError
Error value: 'ascii' codec can't decode byte 0xd6 in position 0: 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 2336, in manage_PropertiesWizard
Module Shared.DC.Scripts.Bindings, line 313, in __call__
Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
Module App.special_dtml, line 178, in _exec
Module DocumentTemplate.DT_Let, line 76, in render
Module DocumentTemplate.DT_In, line 703, in renderwob
Module DocumentTemplate.DT_Util, line 196, in eval
- __traceback_info__: _
Module <string>, line 0, in ?
UnicodeDecodeError: 'ascii' codec can't decode byte 0xd6 in position 0: ordinal not in range(128)
1 year and 3 months and 13 days old
After reading the eror log again I did some testing.
This error only occurs when adding a Section name in step 2 Labeled "Övrigt".
Are international charactes in section names not supported?
Hi.
I have set up a test instance of issue tracker at /TEST
I created a secondary instance at /RSD
Both of those worked perfectly to add and manage issues.
I set up email on the /TEST database and notifications work perfectly. Each user receives an email when they are assigned a task and the tell-a-friend feature works as well
My issue is that I tried to set up email on the /RSD database. The tell-a-friend feature works perfectly but no one ever gets an email with a new assignment. I also went to the mail server logs and I can see the traffic for the tell-a-friend, but never anything at all for the standard notification.
I'm sure this must be a config issue, but I dont have a clue where the feature I missed on the /RSD database is.
to top it off I tried creating a third instance at /ITP and I get the same problem as on the /RSD database. The tell a friend feature works, but not the new assignment email.
Help!
1 year and 4 months and 3 weeks old
Hmm... Strange. I think that when you assign an issue it creates a notification object (e.g. notification00001) inside the issue. So, (in /RSD) go to an issue where you have assigned someone and thus expect an email. Look at any of the notification objects in there and when you click on them and see all the properties you should be able to see a little checkbox at the bottom called "dispatched". What does it say? Is it checked or not?
What version are you running and if you use svn, what revision?
Hi, Thanks for the quick response.
Version information:
IssueTreacker version: 0.10.2
# Zope version: (Zope 2.11.1-final, python 2.4.4, win32)
# Python version: 2.4.4 (#0071, Oct 18 2006, 08:34:43) [MSC v.1310 32 bit (Intel)]
# System Platform: win32
# SOFTWARE_HOME: C:\Zope\2.11.1\Zope\lib\python
# INSTANCE_HOME: C:\Zope\Instance\2.11.1
# CLIENT_HOME: C:\Zope\Instance\2.11.1\var
# Process ID: 1444 (768)
# Running for: 4 days 12 hours 56 min 58 sec
I went into my working version /TEST and was able to locate the notification object and review the notification data...it made sense.
After that I went into my /RSD instance and there was no notification data on any of the issues, all of which should have had an assignment that was notified.
I'm assuming this means that notification is mis-configured. What would be my next step in identifying what I need to correct this?
Thanks Again for the help!
So, there is nothing wrong with the sending of the emails. It's just that notifications aren't created. Can you keep an eye on the event.log whilst you add assignments and see if shows any warnings or anything like that to explain why notification objects aren't created.
We might need to investigate what's going on with the checkbox that is next to assignment.
Thanks!
I restarted Zope and cleared the event.log file and the Z2.log file
After a restart I changed an assignment in the /RSD instance. I did this from a browser that was already open so that I could capture just that change.
I have attached a file called: event_RSD_instance.log
This is the event log file immediately after I changed an assignment in the RSD instance. there is really nothing in that file at all.
I have also attached a file that included the data in the Z2 log file at that time. It has more data, but I think is still only showing the GET/PUT requests that Zope receives.
Is there a physical event file somewhere on a per instance basis?
Is there a process to turn on detailed logging? If so I could log a successful change of assignment and a failed one.
Thanks Again
-Richard
Okay,
I did some more research on this. I think you have a logic bug in the notification process. I will try to detail two scenarios for you. One sends a notification, one does not.
Setup details:
User1: -> me, my email address
User2: -> a test employee, his email address
Issue: -> Issue #0001, exists and is assigned to User2
Scenario 1:
Using the details as listed above; I login as me (user 1) and change ownership to me for issue #0001. Result: no notification is sent
Scenario 2:
Using the details as listed above; User 2 logs in and changes ownership of Issue#1 to me (user1). Result: I get a notification email to user 1.
I can follow this up with me logging in after the email and changing the assignment back to User 2, and he will get an email too.
Working theory:
The end result is it appears as if the system is checking to see if the new assignee has the same email address of the active user and if so it does not send a notification email. The reason this bug is/was frustrating was that I had set up a number of test logins, but all of these had my email address for notification purposes. So every time I sent a test email it failed. To verify this I set up a second user with a g-mail address. I could then re-assign an issue back and forth several times and it would send a notification every time.
I hope this helps, and thanks for a great product. As soon as we go into production with our issue tracker we will be posting our success story to share with others.
-Richard
Well I don't think that is a bug then. I think it works like it should. It works on the premise that there's no point emailing yourself about something you've done. It's considered rare that people have users with the same email address. And if that is the case it's corner cases. Like people like you testing things.
And it should be part of the Properties wizard.
1 year and 8 months and 1 week old
I was running 0.7.2 version. I tried to upgrade it to latest version like 0.10.2 (using SVN as well as directly) .. After upgrade I press "Update Everything" in management Tab but it gave following error.
i initially thought that this is due to me directly jumping from 0.7.2 to 0.10.2 but i reverted back and tried upgrade to 0.7.3 also and i got the same error. Hence i later decided to work with 0.10.2 SVN version.. I can create new trackers but is not able to do many editing, add new issue and even search operations in old trackers.
details of error:
An error occured when I tried to...
--------------------------------------------------
Error type: AttributeError
Error value: 'NoneType' object has no attribute 'getProperty'
Traceback (innermost last):
Module ZPublisher.Publish, line 101, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 39, in call_object
Module Products.IssueTrackerProduct.IssueTracker, line 1764, in UpdateEverything
Module Products.IssueTrackerProduct.IssueTracker, line 2075, in AssertAllProperties
Module Products.IssueTrackerProduct.Issue, line 632, in assertAllProperties
Module Products.IssueTrackerProduct.Issue, line 229, in getFromname
AttributeError: 'NoneType' object has no attribute 'getProperty'
1 year and 8 months and 10 days 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
2 years and 3 weeks and 6 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.
2 years and 1 month and 3 weeks 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.
I am running 8.3, while I was waiting on a couple patches. I renamed IssueTrackerProduct to IssueTrackerProduct.8.3 and renamed IssueTrackerProduct.svn back to IssueTrackerProduct. Then in the ITproduct folder, I ran svn update. The, I chowned (-r) the directory to the correct user:group. But when I start zope with this folder in place I get the following error message.
This object is broken because the IssueTrackerProduct product that created it is no longer installed or is installed incorrectly. Please contact the product maintainer for assistance.
Note that the data associated with this product has not been lost, and will be accessible again if the product is reinstalled.
and from the root view, my ITproduct instance has a broken icon with a "?" on it saying: helpdesk (This object from the IssueTrackerProduct product is broken!)
I successfully reverted to the 8.3 with no problems. But I wonder if I did an svn update at the wrong time?
2 years and 5 months and 2 weeks old
If it's broken you should get some errors in the event log if the product (from svn) can't be installed. It's important that the name is "IssueTrackerProduct" no matter where it comes from (SVN or .tgz). Any other name with break it.
Look for errors and deal with those. It could be permission related if you've got a complex setup.
If you don't get any errors in the event.log, try clicking on IssueTrackerProduct in /Control_Panel/Products/manage_main
I tried a fresh svn checkout on a dev system with the same specs. This is what the event log says.
2008-04-14T01:09:09 ERROR Application Could not import Products.IssueTrackerProduct
Traceback (most recent call last):
File "/usr/lib/zope2.10/lib/python/OFS/Application.py", line 703, in import_product
product=__import__(pname, global_dict, global_dict, silly)
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/__init__.py", line 13, in ?
import IssueTracker
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/IssueTracker.py", line 133, in ?
from TemplateAdder import addTemplates2Class, CTP
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/TemplateAdder.py", line 123, in ?
from Constants import DISABLE_CHECKOUTABLE_TEMPLATES
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/Constants.py", line 222
'sxi':'sxi.png', 'sxw':'sxw.png' 'rar':'rar.png',
^
SyntaxError: invalid syntax
------
2008-04-14T01:09:10 WARNING OFS.Uninstalled Could not import class 'IssueTracker' from module 'Products.IssueTrackerProduct.IssueTracker'
------
2008-04-14T01:09:13 ERROR Application Couldn't install IssueTrackerProduct
Traceback (most recent call last):
File "/usr/lib/zope2.10/lib/python/OFS/Application.py", line 752, in install_product
global_dict, global_dict, silly)
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/__init__.py", line 13, in ?
import IssueTracker
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/IssueTracker.py", line 133, in ?
from TemplateAdder import addTemplates2Class, CTP
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/TemplateAdder.py", line 123, in ?
from Constants import DISABLE_CHECKOUTABLE_TEMPLATES
File "/var/lib/zope2.10/instance/sandbox/Products/IssueTrackerProduct/Constants.py", line 222
'sxi':'sxi.png', 'sxw':'sxw.png' 'rar':'rar.png',
^
SyntaxError: invalid syntax
------
2008-04-14T01:09:13 INFO Zope Ready to handle requests
I know the date is off, that is a separate issue, but the 8.3 tar file works and is the same
Here are the system settings.
Zope Version
(Zope 2.10.3-final, python 2.4.4, linux2)
Python Version
2.4.4 (#0002, Mar 7 2008, 04:45:43) [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)]
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: 8028)
Process Id
2926 (-1262044272)
Argh!! It was an accident. I managed to check in a python file that had a Syntax error in it. :( Just do a SVN update and try again. I really ought to combine the checkins with running of unit tests.
Updated to build 198, but the menu is broken. Notice the copy and paste of the menu below, there is a duplicate for each menu item overlapping it.
* Home Home
* Add Issue Add Issue
* Quick Add Issue Quick Add Issue
* List Issues List Issues
* Complete List Complete List
* User admin
Also attached is a screenshot.
On the bright side, pop3 retrieval did work. Though it is not formatting the html emails from outlook properly.
Look for any errors in the event log. There's something wrong, perhaps, about how images are installed.
Hi! I'm sorry, I fear I did a Very Stupid Thing and I'm looking for a way to mend it.. Years ago I created an instance of IssueTrackerProduct under Control_Panel, but last week I thought that it would be nice to have it under the root container, so I went ahead and _copied_ the instance via ZMI *shame*.
To my surprise, everything works just fine (save for some minor glitches) except one thing: search. Every search I tried didn't find a thing.. I think this is because ICatalog still contains all the old paths for its elements, am I right? Is there a way to fix them?
Many thanks for your time, and sorry again!
2 years and 7 months and 4 weeks old
An error occured when I tried to edit the properties tab in the ZMI
--------------------------------------------------
Error type: AttributeError
Error value: attachedFile_2
Traceback (innermost last):
Module ZPublisher.Publish, line 101, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 39, in call_object
Module Shared.DC.Scripts.Bindings, line 306, in __call__
Module Shared.DC.Scripts.Bindings, line 343, in _bindAndExec
Module Products.CheckoutableTemplates.CTFiles, line 265, in _exec
Module App.special_dtml, line 175, in _exec
Module DocumentTemplate.DT_With, line 76, in render
Module DocumentTemplate.DT_Let, line 75, in render
Module DocumentTemplate.DT_Util, line 198, in eval
- __traceback_info__: manage_findPotentialBrothers
Module <string>, line 0, in ?
Module Products.IssueTrackerProduct.IssueTracker, line 1067, in manage_findPotentialBrothers
Module Products.IssueTrackerProduct.IssueTracker, line 1094, in _getPotentialBrothers
Module Products.IssueTrackerProduct.IssueTracker, line 1094, in _getPotentialBrothers
Module Products.IssueTrackerProduct.IssueTracker, line 1094, in _getPotentialBrothers
Module Products.IssueTrackerProduct.IssueTracker, line 1077, in _getPotentialBrothers
Module OFS.ObjectManager, line 357, in objectValues
Module OFS.ObjectManager, line 244, in _getOb
AttributeError: attachedFile_2
3 years and 13 days old
Any idea what attachedFile_2 is?
Can you figure out what's on line 1094 and line 1077 in your IssueTracker.py since it's different from my latest version now.
I receive this error when I attempt to add a new issue to a fresh installation of issuetrackkerproduct. I have done a new installation again, but get the same error.
Is this unexpected or am I doing something wrong?
--------------------------------------------------
Error type: NoACLAdder
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 3399, in SubmitIssue
Module Products.IssueTrackerProduct.IssueTracker, line 3537, in createIssueObject
NoACLAdder: No ACL user object found
3 years and 1 month and 2 weeks old
Ah, I see this has been reported before, but there is not resolution posted with the issue. Is there a solution to this? (There must be since this helpdesk is working, right?)
Thanks again
I think I have found the problem. If I don't select an acl_user to have a role of "issuetracker user", I cannot add an issue. It may not be logical for all people, since I for one would assume that an issuetracker manager must also be an issuetracker user by virtue of what he does. Maybe this is logical to zope developers, but it's not for users (At least not all),
Can I suggest that a note be added to the installation instructions to say; "A user must have at least a role of 'issuetracker user' to be able to add a new issue."
Could one of the developer's comment on this ? Because another post suggests that this issue cannot be fixed due to an incompatibility with Plone - thanks
HI,
I installed issue tracker in my system but initially i installed .net frame work version 1.1.4322, after tat wich is running in visual studio 2005. But not running in localhost location, showing some "database error" as error symbol. What can i want to do to rectify that error , please help me as soon as possible
3 years and 2 months and 4 weeks old
#0380 Regarding File uploads
issue-tracker Creation of main file upload directory failed!
what we have to do for uploading a file from an issue. when we uploading any file with an issue is giving above error.
Please anybody suggest me.
3 years and 4 months and 3 weeks old
I'll like to upgrade an older version of IssueTracker (0.4.4b)to a more recent version. I can't access the http://localhost:8080/myissuetracker/manage_ManagementForm panel and use the Update Everything button as suggested on the website - I don't think this version (0.4.4b) has the facility (i tried the url but i kept getting a page not found error). I tried exporting the data in the old version then download and install the latest version, add that to zope and try importing the .zepx back but got an error that the says something about the object not supporting the method. I'm really stumped, is there anyway i can upgrade from this version.
3 years and 4 months and 3 weeks old
If you're upgrading from such an old version you can't use the Update Everything button or anything from within the Zope management interface. Upgrade it the normal way you upgrade Zope products and see if the old Zope objects work with the new software.
Please join the mailing list for more questions about upgrading if you get stuck again.