Capabilities from unselected application sometimes shown as assigned for a role after editing

Description

When deselecting an application when editing a role, and selecting a new application, capabilities and sets for the deselected application sometimes shown as assigned to a role. Does not happen for every application/capabilities combination.
Below is a scenario to reproduce this on evrk2. This exact scenario was working as expected for a long time (related tests are automated).

Preconditions:

Authorization role with only the following capability set assigned to it exists in the system:

  • application: 'app-platform-complete',
    table: 'Data',
    resource: 'Calendar',
    action: 'View'

Steps to reproduce:

  1. Log into evrk2 as an admin user

  2. Go to “Settings“ → “Authorization roles“

  3. Find and open detailed view of a role from Preconditions

  4. Click on “Actions“ button in the third pane → Select “Edit“ option

  5. Click on “Select application“ button

  6. Deselect “app-platform-complete“ app

  7. Select “app-platform-minimal“ app

  8. Click on “Save and close“ button in modal

  9. Select the following capability set:

    1. application: 'app-platform-minimal',
      table: 'Settings',
      resource: 'UI-Tags Settings',
      action: 'View'

  10. Click on “Save & close“ button

  11. In role’s detailed view, expand “Capability sets“, “Capabilities“ accordions

Expected result:
Only capabilities/sets for “app-platform-minimal“ app are shown (specifically, a set selected at Step 9, and capabilities in contains)

Actual result:
Capabilities/sets for “app-platform-complete“ and “app-platform-minimal“ apps are shown (specifically, sets selected in Preconditions and at Step 9, and capabilities they contain)

Additional information:

  • The faster the steps are executed, the higher a chance of this issue appearing

  • Adding waits for several seconds in auto-tests (and executing steps a bit slower manually) alleviates the issue

  • Was NOT able to reproduce on FSE Dry run 1

  • See example:

 

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

4

Checklist

hide

Activity

Show:

Yury Barsukou February 12, 2025 at 1:00 PM

Revalidated on bugfest. Fixed. Video added

Yury Barsukou February 3, 2025 at 1:04 PM

Fixed on snapshot, need to revalidate on bugfest after deployment

Yury Barsukou January 24, 2025 at 9:57 AM

Can be stably reproduced on both snapshot and bugfest. Autotest team added some timeouts as workaround, so the problem exists but doesn’t affect them, at least now

Craig McNally January 23, 2025 at 8:44 PM

when you get a chance can you please retest this in snapshot and bugfest? I’d like to understand if this is still an issue. Thanks!

Craig McNally September 6, 2024 at 7:41 PM

TODO: to clarify the requirements in this issue, or close it and create a new story.

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Eureka

Fix versions

Release

Ramsons (R2 2024) Service Patch #1

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created August 6, 2024 at 7:34 AM
Updated February 12, 2025 at 1:01 PM
Resolved February 3, 2025 at 1:06 PM
TestRail: Cases
TestRail: Runs