@david2 I am sorry for the delay here, myself or someone else on my team will be more responsive on these threads moving forward!
To your questions
Question #1
- That is correct, they are not the same. We will look at updating the documentation to make this less confusing. It does not have a height/width or weight value. The iFrame will be whatever height you specify using the AP.resize or AP.sizeToParent (see https://developer.atlassian.com/cloud/jira/platform/jsapi/ap/). The width is just 100% and should be built to be responsive at any size. Please note the maximum height limit is 1500px. Lastly, the weight property is no longer applied. It is based on when the user installs the app and in the future we will look at showing the content modules based on when the user adds content/displays the iFrame below to account for the weight.
- The “target” attribute for the Issue Content module only has the option for ‘web_panel’ today which is just to denote an iFrame will be loaded below. It is not the same as the seperate Web Panel module. At some point we will want to look at giving other options when you click on the quick-add icon, like showing a modal for example, but that is not coming soon.
- This pattern also exists on the Issue Glance module where you specify the target with the only acceptable value today being ‘web_panel’. We are looking in the near future for the Issue Glance module to display as a modal as an option (like the development panel → commits detail can open in a modal as an example).
Question #2
- Yes, you must keep the original Web Panel with location = "atl.jira.view.issue.left.context” for support of your Connect app on the old issue view. Once you add the new Issue Content module to your descriptor, we will handle when to show either one. If you are on the new issue view, we only look at Issue Content modules and render those. The old issue view only looks at Web Panel with location = “atl.jira.view.issue.left.context”.
- Once a user clicks the button, it should not be showing the existing Web Panel with location = "atl.jira.view.issue.left.context”…if it is, that is a bug and we should fix ASAP. I would love to get a few screenshots / video and discuss more if this is the case.
Question #3
- So, we are just broadcasting that event as a custom event (See https://developer.atlassian.com/cloud/jira/platform/jsapi/events/). So you can use AP.events.on(‘ISSUE_QUICK_ADD_CLICKED’) to listen to that and do something (ideally open a modal and let users add content).
- The Issue Content module does not load on every issue detail view load, unless it is visible then it does. However, whenever a user clicks the quick-add icon to add that iFrame below, we load your iFrame below and broadcast out that event, which you will be able to receive (it comes over after the iFrame is loaded and therefore you can listen via the ACJS bridge).
Question #4
- Yes, it is reloaded (it’s all react now, so will re-render specific areas that need to be re-rendered) on issue modified, transitioned, any edits, etc. Also, when you call refreshIssuePage() it will re-render the issue view, but only re-render the any individual components, like your content or glance so it feels fast. it is no longer a full page reload which is really nice. Also, refreshIssuePage() will reload content modules as well.
I hope this helps. Please let me know if you have any further questions.