Error 500 while renaming requirements

Description

  • Create a requirement,

  • Link it to a Jira issue,

  • Go to Confluence, search, tick, menu "Actions", click "Rename",

  • Change anything,

  • It will produce the following error 500, on the latest version:

Important

Another customer has a 'rename' action that hangs. It may be the same issue, but it is also worth checking why the action doesn't fail straight away, whether it is shut down, etc.

Environment

None

Observations

None
Resolved

Assignee

Unassigned

Reporter

Adrien Ragot (Play SQL / Requirement Yogi)

Labels

None

Participants

None

Fix versions

Priority

Matter of months