Fullscreen
Loading...
 
Skip to main content

Named Lists, Tables, Headers, TOC etc in wiki pages and using them as Tracker Fields

  • Tracker item actions
Trackers
Items
Status
Open
Subject
Named Lists, Tables, Headers, TOC etc in wiki pages and using them as Tracker Fields
Version
12.x
Category
  • Feature request
Feature
Trackers
Wiki Plugin (extends basic syntax)
Resolution status
New
Submitted by
Dimitrios Tanis
Lastmod by
Dimitrios Tanis
Rating
(0)
Description

This is probably a complex feature so I'll try to be as clear as possible.
The term Lists will be used for the rest of the text to describe any structured text inside a wiki page that could be thought of as a group of text describing similar things such as bullet lists, numbered lists, tables, headers, table of contents, etc.

Why?:
Let's say you have some bullet list in a wiki page listing departments in an organization. eg

  • Sales department
  • Customer support
  • Supplies
  • Quality department, etc

That info won't change anytime soon so no need to put them in a tracker, you keep all related info in the wiki page.

Now suppose you want to create an issue tracker that can handle issues per department.
Currently you have to either define a tracker for departments and use an item link OR use a combo box,write the departments by hand.

The problem with that is when a change of departments comes, you'll have to remember where the department names are used and to update them manually.

How?:
The above "problem" could be resolved using named lists.
The author could write the department list in a named list and then when designing the tracker there would be a new type of tracker field type named list where he would define the page and named list name or listID to be used.
When adding a tracker item, that field would be rendered:

  • as a drop down combo box
  • as a radio button list (for single selection)
  • as a checkbox list (for multiple selections)

that would fetch the values from that named list.

How to implement?:
There probably are many ways to implement this but my guess is the easiest is reuse/modify existing wikiplugins so as to keep the simple lists plain.
What needed are:

  • At most two new attributes for each supported plugin: name and id eg for fancylist:

  • A new tracker field type Named list that would parse the defined named list

That field type would take as parameters:

    • The page the named list is in
    • The name or id of the named list
  • Optionally a new tiki feature admin page named lists where all lists names would be listed with name, id, and page.


Proposed list of plugins to be named (in order of preference):

  • PluginFancylist
  • PluginDl
  • PluginFancyTable
  • PluginMaketoc
  • PluginToc
  • PluginBacklinks
  • PluginSort
  • PluginAnnotation (for annotations lists)
  • PluginAttributes


Workaround
Discussed above in why section
Importance
6
Easy to solve?
2
Priority
12
Demonstrate Bug on Tiki 19+
Demonstrate Bug (older Tiki versions)
Ticket ID
5123
Created
Friday 31 January, 2014 01:00:32 UTC
by Dimitrios Tanis
LastModif
Friday 31 January, 2014 01:00:32 UTC


Show PHP error messages