Master-Slave <-> Trackers / Trackerlist / List <-> data management, case management, issue management
- Status
- Open
- Subject
- Master-Slave <-> Trackers / Trackerlist / List <-> data management, case management, issue management
- Version
- 15.x
- Category
- Feature request
- Feature
- Trackers
Wiki Plugin (extends basic syntax)
Dynamic Content - Resolution status
- New
- Submitted by
- Torsten Fabricius
- Lastmod by
- Torsten Fabricius
- Rating
- Description
Hi,
I am working on a few datamanagement projects these days and look deeper and deeper to the boundaries of the Tracker feature and the Trackerlist Plugin.
Walper (Wolfgang) has a huge pro datamanagement in his company aswell and is committing very helpful additions and is doing high quality fixes to existing bumping features.
Now it appears (actually original idea from Wolfgang), that on the output side using Trackerlist, we face some strict limitations, which could be easily solved with a master and slave setup.
Tracker should be interlinkt on the output base (wikipages, trackerlist or list plugins) to provide some kind of "issue reports", "case reports" etc. where trackerlist output is conditionally interlinked similar to dynamic list inside the tracker.
basic idea:
Have two or more trackerlist on a wikipage (optionally paginated or so). the master is on top.
Filter content on the top tracker and dynamically get the related content (to the issue or to the case) viewed below.
In my example use case I see, that it would be important to have the option to print the interlinked output together, for example to print out a full overview of a case to have it physically when the responsible person goes to a court hearing. In Wolfgangs use case it might be mor a report for the customer or so to send out as pdf.
At this point I only did a rough sketch and appreciate ideas and input by other users and devs.
Not my sketched technical solution is what I am focussing on, but instead the idea of the workflow and a good UI/UX for aswell site developers and end users.Thx for any ideas and help from coders.
I am seing more and more that data management would be one crucial killer feature in context of a better respectively a successful marketing of our "beast" Tiki.Best regards to all community members,
Torsten- Importance
- 9
- Easy to solve?
- 4
- Priority
- 36
- Demonstrate Bug (Tiki 19+)
-
This bug has been demonstrated on show2.tiki.org
Please demonstrate your bug on show2.tiki.org
Version: Create show2.tiki.org instanceAbout show2.tiki.orgTo help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
- Ticket ID
- 5589
- Created
- Thursday 12 March, 2015 12:46:37 GMT-0000
by Torsten Fabricius - LastModif
- Thursday 12 March, 2015 12:46:37 GMT-0000
Attachments
| filename | created | hits | comment | version | filetype | ||
|---|---|---|---|---|---|---|---|
| No attachments for this item | |||||||
;){kind=link}
;){kind=link}
;){kind=link}
;){kind=link}