Wim,

I have created JRA-15181 improvement. Please add any further comments to that issue.

Thank you!
Dushan

Hi Dushan,

that might be a good idea, since you agree that it could be improved. Otherwise my remark will just get lost and I might get demotivated to report bugs in the future when they are accepted, but then closed anyway.

regards,

Wim

Wim, you are right. If the reporter is required it needs to be filled in even though it may not be used at all.

As I said before, this is not ideal and could be improved. What would you suggest to do to improve this? We could raise it as a new issue - improvement - and we could log all suggestions there if you'd prefer that.

Cheers,
Dushan

Hi Dushan,

so you are saying that Timothy is wrong? We have to fill in a reporter, even if it will not be used? This is very not user-friendly. People are very scared to fill something in there. Everybody will think the reporter will not be retained.

regards,

Wim

Hi all,

There seems to be a bit of a confusion here.

The reason why the reporter field needs a value is that this field is required. When you check the retain option, the reporters are retained where possible. Depending on your configuration this may not be the case for all issues being moved. For those issue a new (reporter) value needs to be set and that's why the reporter field needs a value set.

JIRA could be a bit smarter & user-friendlier and not require a value in the case when all issues will be able to retain the original reporter. At the moment we see this as a small improvement of the already too complex bulk issue move operation that we could possibly make in the future.

Kind regards,
Dushan

This is a pretty severe error in moving issues (reporter is clobbered). Any word on whether it was fixed?

Hi,

I've managed to reproduce the error that Wim is getting.

The reason is that when trying to do a bulk issue and that there is a required field to be filled in, JIRA would still request for the field to be filled in even if the 'Retain' checkbox is ticked.

Filling in the checkbox manually does solve the problem but only if it is a single issue. Other than that, its not right because it will change all the values of the field to the value which is keyed in. If there are different values of the different issues being bulked move together, there would be wrong data being added.

Field in question is the Reporter field.

Regards,
Timothy

Hi Wim,

I will resolve this issue as "Handled by Support" for now. If this bug is reproducible at JSP-19647, then we'll reopen this issue.

Regards,
Timothy

Hi Wim,

I can't seem to reproduce this bug at our local site. Can we continue to solve this issue here at JSP-19647?

Regards,
Timothy

No, it is not the same although somewhat related maybe. In my case, all permissions are there for changing the reporter. The JIRA interface shows that I can set a new reporter for all the issues that I want to move or I can select the checkbox "retain". When I select retain, the check that a username should be filled into the reporter textbox fails because I leave it empty ofcourse.