Simply spoken, a user can easily report an issue for defined products. You may also use it as a little platform to discuss topics or follow up on tasks. A flexible report form is delivered to adapt it to your needs. Created Reports are added to an issue log (project). Before that they are checked if important values are complete.

The user is informed by a green info box if the issue was added successfully to the log file. A box will be displayed in the event of missing information. The issue gets an unique ID and will be stored to a file. The admin is informed by mail about a new report.

The complete issue list delivers a detailed overview of the reports. The list output is sortable and can be easily reduced (column wise), to fit your needs.

For security reason all HTML tags are stripped away. A small editor provide you some styling elements with own little syntax. By this xsEditor you can define some basics like text-decoration, lists, colors, links etc. for issue descriptions, comments and resolutions. The best way to go is writing the text first and then styling it.

Members of configured 'assign' groups are allowed to directly edit the entries of the issue list. They can see all columns by default. The issue list is sortable on all columns. The email addresses of 'assign' group members are automatically loaded into the lists select box to be easily set as issue related contact. Tickets fall back to 'New' status if the assignee is deleted. It is not mandatory to assign a responsible contact for an issue.

Admin / assignees and comment creator (not necessarily the Issue reporter) are allowed to modify and delete comments within a work log. If a user specific function is available can be seen by the modify Comment slider below the box and on the little delete-icon at the upper right side within the comment area. Modification info per comment displaying the date of change right hand side above the comment box.

Status modifications on the Issue List items are logged into a file (*.mod-log) to easily follow up who changed something and when. Such file will be created by the first modification of a list item per issue. A link will be visible on Issue Details to view the history of modifications.

IssueTracker provids also a Search function with highlighting found matches. You can enter one to multiple words, where each will be searched for. But it is not a search engine like Google so extended search patterns and logics will not work. The result is a list of linked Issues and Comments containing one or multiple words you are looking for.

Simply place the following syntax into the page markup:

====== Report an Issue ======
{{issuetracker>project=myProject1|product=myProduct 1.1,myProduct 1.2|display=form|prod_limit=ON}} 

====== List of Issues ======
~~NOCACHE~~
{{issuetracker>project=your_project|product=Rater|status=all|severity=all|display=issues|view=7|controls=off|myissues=on}}

====== Single Issue Link ======
{{issuetracker>project=project_name|id=3|display=single_issue}}

The optional Report Parameter prod_limit=ON will Limit the product drop-down select control to the Syntax provided products. They have to be configured within plugin configuration too.

IssueList Parameters status, severity, view and display will be set to default (status = ALL, severity = ALL, view = 10, display = ISSUES) if they are not defined.

Combination of status or severity parameters are allowed if they are comma separated:

Example:
--------
{{issuetracker>project=your_project|product=all|status=new,assigned|severity=critical,major|display=issues|view=15|controls=on|myissues=on}}

More information about syntax switches are provided at: IssueTracker description

You are using the IssueTracker?

Please put your link here:

• fcon - IssueTracker

Search and install the plugin using the Extension Manager.

Alternatively, refer to Plugins on how to install plugins manually. Download and extract it as folder issuetracker into your \lib\plugins directory.

For complete list of releases please have a look on fcon IssueTracker - Development History

• control name "ittitle" changed to "title" at syntax.php line 1370 (2017-06-27 20:32)
• fixed [309] Ticket without Title possible (2017-03-20 22:47)
• register controller & handler (2016-06-02 10:53)
• Declaration of register($controller) modified to get rid of a warning (2016-05-26 11:45)
• a few bug fixes (2016-02-26 20:33)
• BugFix [260] Ticket with empty title (2014-12-16 16:56)
• BugFix for [258] Search for TicketNumber not working (2014-12-15 11:28)
• quick-fix for FF browser usage (2014-12-04 13:58)

The following configurations can be done by the configuration manager: Admin ⇒ Configuration Settings ⇒ Issuetracker Plugin Settings

Beside this configuration settings you have the possibility to use your own severity and status icons.
Simply save the picture files as [your status].gif or [your severity].gif and store them into /dokuwiki/lib/plugins/issuetracker/images folder. For example you configured a status “gelöst” instead of “solved” then your image file name schould be geloest.gif. Therefore the German language file contain two lines where German “Umlaute” will be converted accordingly.

If you are using different status text as originally provided then please check plugin/issuetracker/lang/[your language]/lang.php for

 $lang['issue_resolved_status']

It has to be identical (case sensitive !).

Use this plugin to simply create an issue tracking. It owns dokumicrobugtracker 2011-04-13 as initial code base for corrections, which was not working on my installation (Rincewind + Arctic). Probably you noticed the same problems (e.g. edit of entries does not work) and may find a help with this.

1. Report an issue
This is a form shown to the user to provide controls for input of issue information.
Following information are handled:

{{issuetracker>project=your_project|display=form|view=10}} 

2. Issue List
The Plugin delivers an issue list, where admin can configure a restricted view for users. The admin view delivers more details in the table.
Admin is able to modify some entries directly on this output, i.e. admin is able to assign the issue to a member of configured user-groups
(see configuration).

 {{issuetracker>project=your_project|status=all|severity=all|display=issues}} 

Remark: All project files of defined IT data store will be loaded if multiproject config switch is turned on.

3. Issue Details view
For better handling and also accessible for users there is a details view of an issue. Therefore the Issue List containing a input and button to specify the isuue ID. This will provide a new page displaying all information of an issue and delivering a comment function for interaction between User and Admin/assigned resource. Both (user/assignee) will be informed about issue updates by email, if configured.

4. General Info
There are multiple files created. First there is a project file containing all issue information except comments. Each issue will have a comments file where the communication is logged. A modification log provides a history to follow-up status changes (answering the when, who, what). All files are stored to data/meta directory with file extension ”.issue”, ”.mod-log” and ”.cmnts”.

Each valuable help is welcome.

The plugin was tested with DW listed on top of this page and also with related on the Stick version.
My standard browsers are Internet Explorer and Firefox due to majority of users using this.
This is not the guarantee that it works for all environmental configuration.

If you have a wish what should be improved then please register for fcon - IssueTracker and report a feature request.

Please use only the DokuWiki User Forum for discussion and Issue Tracker to raise your problems. You can mention it here but this page is not regularily tracked and if something is solved it will be cleaned from this page (better to use the forum due to automated notifications on an issue).

Partial Russian translation (to Taggic: don't use for GitHub-repository, please).

For collection of FAQ please check: IssueTracker - FAQ

incredibly awesome - thanks for adding this plugin!
by robert

I keep getting the error “Please provide a better description” when trying to create an issue no matter what I do. Is there something I need to change on the configuration?

This is because for some reason, in the syntax.php file at the beginning of the validation function chkFormular, the value of the textfield is set to its innrHTML attribute.

frm.description.value = frm.description.innerHTML

This effectively clears the content of the textarea which thus have no content when it's checked for content funther down in the function. So just comment the above stated row (row 1205) and it all should work.

Issue title not being saved (a bug fix?)
by wagners

First of all, thank you for providing IssueTracker plugin!

I have installed IssueTracker on Dokuwiki (Release 2017-02-19b “Frusterick Manners”) and noted that the issue title was not being persisted in file [my_project].issues when submitting a new issue report. Apparently, I understand this problem as an effect of change #309, since that the problem was solved here changing syntax.php from:

 $issues[$issue_id]['title'] = htmlspecialchars($_REQUEST['title']);

 $issues[$issue_id]['title'] = htmlspecialchars($_REQUEST['ittitle']);