• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.
Name Type Size Values Tooltip message Attributes
One-line summary
Summary text 85     M
Use TWiki:Main.UserName. You will automatically be informed of changes to your report (see WebNotify)
ReportedBy text 60 TWiki:Main.TWikiGuest   M

Codebases on which this problem has seen (please tick all tested)

Codebase checkbox 15 ~twiki4, 6.1.0, 6.0.2, 6.0.1, 6.0.0, 5.1.4, 5.1.3, 5.1.2, 5.1.1, 5.1.0, 5.0.2, 5.0.1, 5.0.0, 4.3.2, 4.3.1, 4.3.0, 4.2.4, 4.2.3, 4.2.2, 4.2.1, 4.2.0, 4.1.2, 4.1.1, 4.1.0, 4.0.5, 4.0.4, 4.0.3, 4.0.2, 4.0.1, 4.0.0    
  label   If you know it, what SVN range (first-last) was this first noticed in? (Required if Codebase is ~twiki4 or ~develop)    
SVN Range text 60 TWiki-6.1.0-trunk, Sun, 02 Jul 2023, build 31075    
Select which area of TWiki development this applies to (use Extension for Plugins, Skins, Contribs etc)
  • Engine the core TWiki code, not including plugins/contribs bundled with the standard TWikiFor (these are Extensions)
  • Extension plugins, skins, contribs, twiki applications - any sources or documentation in the twikiplugins area
  • NotTWiki Issues with something outside the TWiki codebase e.g. Apache setup, browser setup etc.
Please report documentation issues like any other issue, against the relevant component i.e. Engine, Extension. Documentation issues are no different to code issues, and need to be tracked the same way.
AppliesTo select 1     M
If AppliesTo is "Engine" this is the component of the engine affected (e.g. "[[Documentation]]", "[[Configure]]" etc). If AppliesTo is "Extension", please indicate the name of the extension here e.g. "WysiwygPlugin", "MailerContrib", "LanguageFr". The main purpose of this field is so that bugs can be grouped according to specific components, so please try to re-use component names that exist as topics.
Component text 60   If applicable  
| | label | |
  • Enhancement means the issue describes a WIBNIF (wouldn't it be nice if). This is for agreed-upon enhancements only. To raise a proposal for a new feature go to TWiki Feature Proposals .
  • Low means the issue is non-critical, and is really more of an annoyance than anything else
  • Normal means that this is probably a bug, but can be lived with
  • Urgent means it really is a bug, and can't be lived with. An open Urgent will block a release
| | |
Priority select 1     M
  • New the issue has just been found, and hasn't been analysed yet, or there is new data about an existing issue.
  • Waiting for feedback the report was insufficient to analyse the issue, and more feedback is needed from the person named in the "Waiting For" field. Once the reporter has added feedback they should flip the state back to "New". If feedback is not received within 30 days, the issue will be discarded.
  • Confirmed the issue has been analysed, and the bug is confirmed by a developer or second party. The item can henceforth be classified regarding release blocking status etc. Someone needs to pick it up and fix it.
  • Being Worked On the issue has been analysed, and is being worked on by the developer named inthe "Waiting For" field.
  • Waiting for Release the issue reported has been fixed and is queued for release. See the TargetRelease field to see whether it is queued for the next patch, minor, or major release. If the reporter isn't satisfied with the fix, they should flip the state back to "New" and explain why. Note that the Waiting For Release field is used for generating the release note.
  • Closed the issue has been fixed to the satisfaction of the fixer, and has been through the "Waiting for release" state, and is now released to end users. If the reporter isn't satisfied with the fix, they should flip the state back to "New" and explain why. Note that bugs reported against new code (code that has not been released yet) or Extensions (Plugins etc) should jump straight to "Closed" without going through "Waiting for Release" first because we do not want these listed in the TWiki release note.
  • Deferred the issue will not be fixed for the release currently being worked on. The text should explain why.
  • No Action Required the issue was already fixed, or it's a duplicate, or a RTFM, or could not be reproduced and feedback was never received.
Please make sure there is an entry in the details explaining any state change.
CurrentState select 1     M
Use TWiki:Main.UserName
  • If the Current State is "Waiting for Feedback" then this report is waiting for attention from the person named in this field.
  • If the Current State is "Being Worked On" that person is working on this problem (please do not set this on behalf of others! It should only be set by the person doing the work.)
Anyone listed will automatically be notified of changes to the report; see WebNotify.
WaitingFor text 60      
List of the subversion rev numbers that were generated by checkins that referred to this item in the log message.
Automatically maintained, do not modify unless you know exactly what you are doing!
Checkins text 60      
| | label | |
Used where the issue is planned to be incorporated in the next major, minor or patch release.
  • n/a means not confirmed, or refers to an extension that is not part of a standard TWiki release, or it hasn't been decided which release to target yet, or the fix was required because something broke in a prior bugfix.
  • patch refers to the next bugfix release, and should be used for urgent bugfixes and minor corrections only.
  • minor refers to the next maintenance release, and may be used for minor functionality improvements and refactoring.
  • major refers to the next full release, and should be used for all functionality changes, and any deprecations.
This field should only be set by developers and the release manager! It is not a prioritization field, it is for tracking the known contents of planned releases.
| | |
TargetRelease radio 4    
First codebase in which the problem was fixed. (Can only be trusted for 4.1.1. and later.)
ReleasedIn checkbox 15 6.1.1, 6.1.0, 6.0.2, 6.0.1, 6.0.0, 5.1.4, 5.1.3, 5.1.2, 5.1.1, 5.1.0, 5.0.2, 5.0.1, 5.0.0, 4.3.2, 4.3.1, 4.3.0, 4.2.5, 4.2.4, 4.2.3, 4.2.2, 4.2.1, 4.2.0, 4.1.3, 4.1.2, 4.1.1, 4.1.0, 4.0.5, 4.0.4, 4.0.3, 4.0.2, 4.0.1, 4.0.0    

Edit | Attach | Watch | Print version | History: r92 < r91 < r90 < r89 < r88 | Backlinks | Raw View |  Raw edit | More topic actions
Topic revision: r92 - 2018-07-17 - PeterThoeny
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback