プロジェクト

全般

プロフィール

Vote #73539

未完了

Copy multiple issues faild

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

ステータス:
Needs feedback
優先度:
通常
担当者:
-
カテゴリ:
Issues_2
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
2
version_id:
0
issue_org_id:
13440
author_id:
74258
assigned_to_id:
0
comments:
5
status_id:
10
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[Needs feedback]

説明

I have the following error message when I copy two issues at the same time : #377 and #378 : Failed to save 2 issue(s) on 2 selected: #, #.
I found nothing in log file : production.log

I use the same share version in both projects.

If I copy only issue #377 it works fine, If I copy only issue #378 it works fine also.

I have also a “task” tracker and copy multiple issues is works fine

Version description :
Environment:
Redmine version 2.3.0.devel
Ruby version 1.8.7 (x86_64-linux)
Rails version 3.2.12
Environment production
Database adapter Mysql2
Redmine plugins:
rhodecode_repo 1.1.1


journals

Does this happen when you click 'copy', or when you save the data afterwards?
--------------------------------------------------------------------------------
Errors should now be logged after r11611. Could you update and retry then post the validation errors?
--------------------------------------------------------------------------------
The error happens after these actions :
* select two issues in project "training"
* click right mouse then select copy
* modified the project to "test"
* click on copy, then the error message arrive

we install the release ; 2.3.0.devl on the trunck

Environment:
Redmine version 2.3.0.devel.11621
Ruby version 1.8.7 (x86_64-linux)
Rails version 3.2.12
Environment production
Database adapter Mysql2
Redmine plugins:
rhodecode_repo 1.1.1

--------------------------------------------------------------------------------
alain Spriet wrote:
> [...]

Please post the validation errors like J-PL requested...
--------------------------------------------------------------------------------
I see in production.log : *issue could not be updated or copied: Criticality can't be blank

The criticality is a custom field required but in the initial issue( #377) the criticality is set.
if I modified the criticality before copy I can copied the issue.
If i selected only one issue the copy works fine without modified the criticality before copy. I have the error only if i selected multiple issues without modified custom field required.

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

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

  • カテゴリIssues_2 にセット

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

いいね!0
いいね!0