|Anonymous | Login | Signup for a new account||2019-10-15 18:31 BST|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000919||SiT!||incidents||public||2009-08-31 15:43||2009-09-11 17:09|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0000919: Strange SiT! markup fields in incident overview?|
|Description||This is really a very minor issue to me. But, because I've reported it in the Forum I didn't want to let it fade away.|
I can reproduce the following bug ONLY when I have disabled "Portal can create Incidents?" (= set to False) in the configuration panel (Features/Portal). Although a portal contact is able to fill out the details to report an issue, it will get registered and placed in the Holding que for the Administrator. The Administrator can create an issue out of it or unlock? it.
Filling out the incident form by a contact (by using the "Add incident" button or by choosing directly from the menu), after submitting the enters given in the comment area will get transformed into strange SiT! markup code. You only see them after reopening the incident, not during typing. When the incident is made and you open it again from the "Your current open incidents" list, the enters previously made are looking like this:
I've tested it in all browsers (Firefox, Safari and Internet Explorer) and all gave the same strange looking "SiT! markup code".
Further updates (by contact and by user) seems to be ok. No transformations of enters given occurred. So it seems like it only applies when a new incident is being made by the contact.
P.S. It seems to me contacts shouldn't see the "Add incident" option when in the configuration panel (Feature/Portal) the feature of creating incidents is disabled.
|Tags||No tags attached.|
|Thanks for the report, I've reproduced this on my test system|
|The "Portal can create Incidents" option does not allow the add incident feature to be disabled completely, rather it changes the behaviour of the portal add incident form. When set to TRUE the form creates Incidents, when set to FALSE the form creates incident requests in the holding queue instead. I've changed the wording to make this a bit clearer and updated the docs.|
|2009-08-31 15:43||lextof||New Issue|
|2009-09-11 16:22||ivan||Status||new => confirmed|
|2009-09-11 16:22||ivan||Note Added: 0001936|
|2009-09-11 16:22||ivan||Target Version||=> 3.50|
|2009-09-11 17:05||ivan||Note Added: 0001937|
|2009-09-11 17:09||ivan||Target Version||3.50 =>|
|Copyright © 2000 - 2019 MantisBT Team|