Links to embedded issues are not fully displayed
Description
Example share page with embedded issue link
https://confluence-prd-1.kz-test.ovh/content/c6275130-7597-40f3-93b2-caeb73c19e36/2490369/5734401
- Smart links (direct links)
- Jira issue macro (single and filter and count of issues)
- Agile wallboard (boards - Agile Walboard Gadget)
- Work management link embeddings
- Board
- List
- Timeline
Linked issues
is duplicated by
ESFJ-790
Error while rendering Jira board/timeline from ESFC shared page
Released
ESFJ-795
Jira board/timeline/list displayed on ESFC shared page is cut off
Withdrawn
Activity
Show:
Hello @Miłosz Jaskólski,
Please merge code to dev branch.
This is the best moment to add more information that can be helpful to prepare release notes.
Can you prepare short overview of change that can be used in release notes?
Please provide short GIF that showcase feature.
If GIF make no sense, can you provide image that highlights feature that can be used in release notes (cropped & annotated)?
@Miłosz Jaskólski Fix verified - QA environment.
@Sagar Rawat all macros in supported section should display correctly now
@Sagar Rawat can you give @Miłosz Jaskólski more info on what needs to be fixed ?
@Miłosz Jaskólski https://ces-qa.warsawdynamics.com/content/9df8feb6-01ea-4221-970b-4a55b0b39cd1 . Supported macros should be displayed correctly on shared pages as discussed on call. Currently filter/legacy macro are not sized correctly on shared pages.
@Sagar Rawat what is the of status of this issue ?
@Miłosz Jaskólski As per your request
https://ces-qa.warsawdynamics.com/content/585324c3-3b75-457f-96da-d0c1341b7ec0
@Miłosz Jaskólski Fix failed - QA environment. Links are still not displayed fully on shared pages.
Error details: Failed to load resource: the server responded with a status of 404 (Not Found)
chromewebdata/:1 Refused to display 'https://parsashivaqa.atlassian.net/' in a frame because it set 'X-Frame-Options' to 'sameorigin'.
Hello @Miłosz Jaskólski ]
This is the best moment to add more information that can be helpful for tester.
What areas are affected?
What are potential edge cases?
Was it checked for XSS problems?
Does change affect security, is new data exposed?
Please attach - Before / After screenshot if possible.
Hello @Miłosz Jaskólski,
Change was reviewed and approved.
Task is ready to be deployed to QA.
Once it is deployed to QA please move ticket to "To Test"
Thank you!
Hello @Krzysztof Bogdan,
Task is ready for review.
@Miłosz Jaskólski please make sure reviewer
have easy access to contend to be reviewed.
If this is code change. Please make sure PR is created.
If this is new documentation, blogpost, etc. Please provide link to page.