Work Item View 2.0 for Ecosystem Partners

Hey @m.herrmann , can you please share us a loom video of the issue you are facing?

Hi Neel, thanks for picking this up.

The app is MSG/EML Email Viewer for Jira (cloudscript.io), on the Marketplace at https://marketplace.atlassian.com/apps/463039643/msg-eml-email-viewer-for-jira. The current production version declares one jira:issueContext module (Custom UI) titled “Attached emails”, with a label and dynamicProperties pointing at a function that returns a count badge. To trigger it, attach any .msg or .eml file to a work item: in the classic view the collapsed group header shows the count; in the new view it does not. If you need anything from our side to install or reproduce, tell me.

One thing that should save you time: my follow-up in post 8 (posted from my other account, NatashaCloudscript) has the instrumented result. In the classic view, loading the work item sends a useDynamicPropertiesMutation request for the module and the function logs its invocation. In the new view, same work item and same user, there is no useDynamicPropertiesMutation request at all and the function never runs, whether the Apps section is collapsed or expanded at load. The panel body loads normally through its own resolver, so this looks like the new view not requesting dynamic properties for context modules rather than a rendering problem.

Two points from my original post remain open:

  1. Is label intentionally no longer rendered in the Apps section, or is that part of the same fix?
  2. Thanks for confirming the Apps menu button for jira:issueActivity on desktop. At narrower widths I observed the app’s activity view inside the All / Comments / Work log dropdown instead. Is it still reachable there, or does it drop off below the desktop breakpoint?

Thanks,
Natasha

Hey @NeelDedhia, can we please get an update on the dynamic status property fix? When will it be shipped? We are getting customer requests asking what happened to the feature.

This is getting frustrating. I expect Atlassian to fix these issues quickly or STOP the rollout of the new issue view. These issues were reported here a month ago, and nothing has happened.

Please test your own changes and stop deploying everything in YOLO mode. I am getting tired of being Atlassian’s human tester and bug reporter. AI is good and all, but please use it responsibly.

Below is a new issue I just noticed. Color and border-radius appear incorrect in dark mode:


Hi @NeelDedhia , thanks a lot for following up and for rolling out the fix. I’ve verified it on our side and the issue is resolved: our app now works as expected in the new work item view. We really appreciate the help. If we run into anything else, we’ll let you know.

Thank you for confirming the fix

Hi @RiturajSeal and @NeelDedhia

Thanks for the follow-up. One correction to my earlier confirmation: the fix works on one of our sites, but on a second (developer) site the issue still reproduces.

On the affected site, clicking a checkbox inside our Forge custom field’s edit view (issue view, field pinned by admin) closes the Jira frontend version (1.476723.0-4fbbff2fb74fbc).

Other differences on the affected site that may help:
- The “Modern work item view” beta toggle has no effect. When we turn it off, the modern view still shows.
- The beta features list is different. For example, “New board experience for company-managed spaces” is missing.

So it looks like that site hasn’t received the fix yet, maybe because it’s in a different rollout cohort. I can share the site URL and a Playwright trace privately if that helps.

Hi @emrekaraduman ,
We have started the rollout of the fix today, so it might be still reproducible in some sites. The rollout will be completed by next week

Hey @NatashaCloudscript , thanks for sharing the app name and more context around this issue. We are working on fixing this, and will share an update in this thread once the fix is rolled out.

Hey @tbinna apologies for the delay, regarding dynamicProperties issue we are actively working on it, Ill update the thread here once the fix is ready for the rollout.

Regarding the color and border-radius issue, is there any other app from intercom where in you seeing this issue?

Thanks @tobias.viehweger, for flagging FRGE-2260. We’ve looked at it. It’s a valid feature request, and it applies to both the old issue view and the new work item view, not just the new one.
Our current focus is fixing bugs for the work item view GA fast-follow, so we can’t commit to this one right now. We’ve logged it for triage after that work and will update the ticket when we have a timeline. Please keep adding use cases and customer impact on the ticket, since that helps us prioritise it.

Hey @NeelDedhia, we don’t have another app available in the sidebar on that Jira instance. However, when I look at work items on https://ecosystem.atlassian.net/jira/browse, it works correctly, and the left/right spacing issue seems to be resolved there too. I have sent you another DM with that Jira instance where we see the border radius and color issue.

Hey @tbinna we have started rolling a fix with regards to padding issue. The rollout is in progress. The fix was enabled for https://ecosystem.atlassian.net/jira/browse hence you are seeing the padding for apps correctly. I have also explicitly enabled the fix for the instance url you shared with me in DM. Can you please verify and let us know if that instance also has the padding issues fixed. Thanks !

@NeelDedhia Any updates on this?

Hi @NeelDedhia thanks for the update. For us, the spacing issue is not fixed. There’s still 8px of left padding (if disabled, other CSS kicks in and adds 19px of left padding).

The border radius issue in the header is still present when viewing the work item in a pop-over/center view. Appears to be fixed in the full-page view and the sidebar.

Please install our app or create a sample app to verify your own changes.

Hi @tbinna ,
Can you please share a screenshot of the padding issue you are facing, we are unfortunately unable to replicate this

Hi @RiturajSeal

Screenshots below. It’s better than before, but not pixel-perfect. The yellow padding from a diff outside the iframe is too big. As shown in the second screenshot, the content in the iframe doesn’t align with the app logo, which I think was the intention.