[
https://issues.apache.org/jira/browse/SYNCOPE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836544#comment-17836544
]
ASF subversion and git services commented on SYNCOPE-1813:
----------------------------------------------------------
Commit 389a4189052b998bda4affe01001ef2c04fd1dd0 in syncope's branch
refs/heads/3_0_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=389a418905 ]
[SYNCOPE-1813] Ensuring (de)provision results are sorted according to request
> Wrong provisioning result shown after batch operation
> ------------------------------------------------------
>
> Key: SYNCOPE-1813
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1813
> Project: Syncope
> Issue Type: Bug
> Components: console
> Affects Versions: 3.0.6
> Reporter: Andrea Patricelli
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Fix For: 3.0.7, 4.0.0
>
>
> # Login in console as admin
> # Click on user and then manage resources
> # Select two or more resources which should go into different propagation
> outcomes and then click on the gear to execute a batch operation. E.g. if you
> run in embedded mode use ws-target-resource-nopropagation2 and resource-testdb
> # Run provision and you'll see the result window with wrong outcome order:
> result should be resource-testdb -> FAILURE and
> ws-target-resource-nopropagation2 -> NOT_ATTEMPTED. It's the opposite,
> instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
