プロジェクト

全般

プロフィール

Vote #63005

完了

Make issue description non-required field

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

ステータス:
Closed
優先度:
通常
担当者:
-
カテゴリ:
Issues_2
対象バージョン:
開始日:
2008/04/08
期日:
進捗率:

0%

予定工数:
category_id:
2
version_id:
6
issue_org_id:
1014
author_id:
574
assigned_to_id:
0
comments:
6
status_id:
5
tracker_id:
2
plus1:
1
affected_version:
closed_on:
affected_version_id:
ステータス-->[Closed]

説明

Maybe others will no agree with me, but lot of issues I create is filed with "x" or simillar balast in description field, because sometimes I'm deadly descriptive with Subject only ;)

Or, it can be put into Redmine's main configuration so admin will decide if Description is required or not...


journals

+1 I tend to copy and paste the subject into the description which is really annoying
--------------------------------------------------------------------------------
Patch attached with unit test.
--------------------------------------------------------------------------------
Changes seems to work fine, however the patch file has some "git references" and I couldn't just "cd trunk" then "patch -p0 < allow_empty_descriptions-1014.diff".
Here goes another patch file.
--------------------------------------------------------------------------------
Thank You, Eric. So it seems I have to learn how to deal with .diff files ;)
Because we're using SVN to upgrade our Redmine, dosen't create some conflict states after updating SVN when usinf diff'ed files?
And why not to use this modification in trunk?
Thanx!
--------------------------------------------------------------------------------
bq. Because we're using SVN to upgrade our Redmine, dosen't create some conflict states after updating SVN when usinf diff'ed files?

It shouldn't create a conflict unless the same files where modified in SVN. You can also back out any patches before upgrading by following these steps:

# Apply patch
@patch -p0 < the-patch-file.diff@
# ... some time later ...
# Reverse the patch
@patch -p0 -r < the-patch-file.diff@
# Upgrade SVN copy:
@svn update@
# Reapply the patch to the updated code:
@patch -p0 < the-patch-file.diff@

bq. And why not to use this modification in trunk?

I don't have permissions to commit to SVN directly.

--------------------------------------------------------------------------------
Done in r2246.
--------------------------------------------------------------------------------


related_issues

relates,Closed,2456,Dont require a Description for every issue

Admin Redmine さんがほぼ2年前に更新

  • カテゴリIssues_2 にセット
  • 対象バージョン0.9.0_6 にセット

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

いいね!0
いいね!0