Project

General

Profile

Actions

Feature #4469

open

custom string field having wiki pages

Added by Kihyun Yun about 14 years ago. Updated almost 14 years ago.

Status:
New
Priority:
High
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
2009-12-22
Due date:
% Done:

50%

Estimated time:
Resolution:

Description

If a string field has value which are wiki pages, it is very useful to improve relationship between wiki pages and issues.

If it is possible, I can use this fields the following purpose.
  • Related Requirement
  • Related Design
  • Related Customer
This wiki string field must have some user interface features.
  • link to wiki pages.
  • If linked wiki page is not exist, show it some differently, red?.
  • If this field has an option, which is "view the fragment of page", linked wiki pages are displayed with overflow style sheet property that has "none" value.
  • If this field has an option, which is "multiple", several wiki pages can be used as value with comma.

It is possible?

I tried(reviewed) some AGILE plugins which have backlogs and so on. But I found Wiki is more useful.
Each issues are scattered but wiki pages are central and version controlled by Redmine.

If it is possible, the wiki pages can have a macro, which is named "{{related_issues(optional field names)}}".

Is it NICE?

Thanks.

Actions #1

Updated by m m about 14 years ago

  • Assignee set to Azamat Hackimov
  • % Done changed from 0 to 50
Actions #2

Updated by Emmanuel Charpentier almost 14 years ago

We looked into this from possibly another point of view, could it be useful?

See #5250, where basically we change custom text rendering so that it goes through textile transformation every time...

Actions #3

Updated by Kihyun Yun almost 14 years ago

Emmanuel Charpentier wrote:

We looked into this from possibly another point of view, could it be useful?

See #5250, where basically we change custom text rendering so that it goes through textile transformation every time...

Sorry, I may helpful for wiki link in a issue view.

But my suggestion is focused on relation between WIKI and ISSUES.
I guess the WIKI central development processes.

One requirement will be changed by several stakeholders and developers.
And its issues are scattered in a project. But if all issues on this requirement has relations to the requirement WIKI page, users can track the changes of the requirements and its solving status.

Thanks a lot.

Actions #4

Updated by Azamat Hackimov almost 14 years ago

  • Assignee deleted (Azamat Hackimov)
Actions

Also available in: Atom PDF