Details
-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
None
Description
Summary
In certain situations when attempting to update an issue through SOAP or in the GUI, the below error is thrown:
customfield_xxxxx=Epic with name 'TEST-1' is not unique
Steps to Reproduce
Setup an instance so that it has epics with the following IssueKey configurations:
- TEST-1
- TEST-10
Update an issue using SOAP's UpdateIssue:
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://soap.rpc.jira.atlassian.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"> <soapenv:Header/> <soapenv:Body> <soap:updateIssue soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <in0 xsi:type="xsd:string">efdf6949a440090fbc4c7a9cef2f9c5e9bae57b4</in0> <in1 xsi:type="xsd:string">TEST-1</in1> <in2 xsi:bean="http://beans.soap.rpc.jira.atlassian.com"> <RemoteFieldValue> <id>description</id> <values> <values> Test 123 </values> </values> </RemoteFieldValue> </in2> </soap:updateIssue> </soapenv:Body> </soapenv:Envelope>
Get in0 from the login method and replace in1 with the appropriate issuekey.
Expected Results
The issue is updated.
Actual Results
The above error is thrown.
Workaround
Cloning the issue and closing the original can help with the problem as it will move the issuekey out of the matching range. For example, if TEST-10 is cloned into TEST-21 it will no longer conflict with TEST-1.
Notes
This is also covered in further detail in "Epic with name 'xxxx' is not unique" error when trying to add an issue to an epic.
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-