[Fleet]: "Upgrade package policy" button navigates user to Edit Integration page.

[amolnater-qasource]

Kibana version: 7.15.0 BC-2 Kibana Cloud environment

Host OS and Browser version: All, All

Build details:

Build: 43742
Commit: 113d5f2a745ab9be7d567d13ff906dfd0f5b7a9a

Preconditions:

1. 7.15.0 BC-2 Kibana Cloud environment should be available.
2. Lower version Apache integration should be available, say 0.5.0.

Steps to reproduce:

1. Login to Kibana environment.
2. Add Lower version Apache integration to Default Policy.
3. Observe v0.5.0 version Apache added to Default Policy.
4. Upgrade Apache integration from Settings, i.e, v0.8.1.
5. After successful upgrade navigate to Default Policy and click Upgrade package policy button available under Actions for Apache integration.
6. Observe user is navigated to Edit Apache Integration page.

Note:

• This issue is observed for all integrations with lower versions.

Expected Result:
Upgrade package policy button should navigate user to Upgrade Integration page.

Screen Recording:

7.13.4.Policy.with.Integrations.-.Agent.policies.-.Fleet.-.Elastic.-.Google.Chrome.2021-08-26.15-43-39.mp4

Expected Page:

Reference Ticket:
#107171

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[amolnater-qasource]

@manishgupta-qasource Please review.

[manishgupta-qasource]

Reviewed & assigned to @kpollich

CC: @EricDavisX

[EricDavisX]

can we re-test this on the next passing 7.15 snapshot build please? I expect some fixes may not have made it to BC2 - but are *I think already fixed. I'm not sure if this is similar to what was reported against BC1 ? @amolnater-qasource @dikshachauhan-qasource ? If so, I'm hopeful it is fixed. Maybe - let's check it.

[kpollich]

@EricDavisX - This one was actually a bug in the latest. I pushed a quick PR to fix this link this morning. Thanks for pinging here! Will be closed out later today 🙂