-
Bug
-
Resolution: Fixed
-
Low
-
None
-
Severity 3 - Minor
-
NOTE: This bug report is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? See the corresponding bug report.
Summary
Committing issues in portfolio returns an error due to wrong user-property for the reporter field. This error is caused by changing the username where user-key is not equal to the username.
Environment
- Version: 1.12.4-OD-D20160322T001113
Steps to Reproduce
- Create issue to Portfolio plan
- Click on the Uncommitted change button to sync with JIRA
Exception when trying to commit a created ticket
com.atlassian.jpo.scenario.common.data.ScenarioCommitException: Scenario commit error Caused by com.atlassian.jpo.env.issues.EnvironmentIssueCreateException: Specific error details : {reporter=The reporter specified is not a user.} at com.atlassian.jpo.env.issues.JiraIssueService.createIssue:302 at com.atlassian.jpo.env.issues.JiraIssueService.createIssue:92 at com.atlassian.jpo.scenario.issue.ScenarioIssueCreateAction.performApiOperation:53 at com.atlassian.jpo.scenario.issue.ScenarioIssueModificationAction.perform:185
Expected Results
Issue is synced successfully
Actual Results
Issue is not synced and error change couldn't be synced shown
Workaround
The user could change their username to be equal to the initial one, which is the user-key
- is duplicated by
-
JSWCLOUD-19110 Exception when attempting to commit the creation of new Initiatives or Stories in Jira Portfolio Labs
- Closed
- is related to
-
JPOSERVER-1356 Issues created in Live Plans cannot be committed due to wrong user-property for the reporter field
- Closed