プロジェクト

全般

プロフィール

Vote #66241

未完了

custom string field having wiki pages

Admin Redmine さんが約2年前に追加. 約2年前に更新.

ステータス:
New
優先度:
高め
担当者:
-
カテゴリ:
Custom fields_14
対象バージョン:
-
開始日:
2009/12/22
期日:
進捗率:

50%

予定工数:
category_id:
14
version_id:
0
issue_org_id:
4469
author_id:
2499
assigned_to_id:
0
comments:
4
status_id:
1
tracker_id:
2
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

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.


journals

--------------------------------------------------------------------------------
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...
--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

Admin Redmine さんが約2年前に更新

  • カテゴリCustom fields_14 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0