It’s time to dogfood your apps with the new approach to Confluence Cloud macros!

Confluence Development Confluence Cloud Announcements
, ,
21

@JonnoKatahanas Nice update! It’s way more easy to add macros right now than constantly clicking the “View more” menu or the edit button after insert it by the shortcut :slight_smile:
However, same problem here: there is no edit button. When should we expect this to be addressed?

51
51818×321 15.8 KB

22

Hey @PhilipFeldmann @TomHarris @lfcgomes - We’re working on a fix for this as we speak. Thanks for raising. This issue won’t reach customers.

4 Likes
23

Hey @BobBergman @jeff @TureHoefner! We’ve already fixed this (i.e. it falls back to historical config), we’re just waiting for the deployment to land in your instances. It should be out by EOW at the latest. We’re working to try and expedite this even faster. There’s been a delay in deployments because of public holidays in the US. This issue won’t reach customers. Sorry this has caused issues with some integration tests.

To re-iterate, we are treating this as dogfooding to stress-test and find issues we need to fix before going to customers. No customer/end user sees what we’re sharing with you. It’s not an EAP that will land for customers.

3 Likes
24

@BobBergman thanks for raising. We’ll wait for more information.

2 Likes
25

@BobBergman if you can PM me or email me (jkatahanas@atlassian.com) the instances affected, we’ll turn the feature off until it’s fixed. We’ll then turn back on. We 100% don’t want to block your integration tests.

2 Likes
26

@JonnoKatahanas Thank you for the update.

27

We are experiencing an issue with a macro with rich-text body and custom editor: AP.confluence.getMacroBody() always returns <p /> instead of the actual body.

10 Likes
28

Thanks @JonnoKatahanas for the update and quick response. It doesn’t really feel like dogfooding for stress-testing in this case given the fundamental and broad range of issues discovered. It’s great it was discovered by the vendor community but does make for some concern as well. It feels a bit like the team is too narrowly focused on a few different macro use cases and these types of rollouts could be avoided with a little broader perspective. I’m sure you have the data that can tell you all the different macro types in use in cloud. I understand that your team is likely not managing a bunch of Connect app/macros and tests for them, even though they are readily available in the Marketplace, so if you ever need to seek some advice on testing strategies and such please let me know. We are definitely here to help. Thanks again!

2 Likes
29

Hey @akhaneev, your issue doesn’t look related to this feature. Is it possible for you to try it in another instance where this feature is not on?

30

Hi @rifat, this issue reproduces in two of our dogfooding instances and can’t be reproduced in another instance that is not in the dogfooding group. We noticed the issue this Monday and it worked fine last Friday.

31

Hi @JonnoKatahanas ,
We are testing the new macro feature and unfortunately it seems to breaks our Balsamiq Wireframes macro view as shown here:

https://recordit.co/B7l1CfnpXe

From what we can see, the code of our app is not even invoked. We are using a “dynamicContentMacros” module and these are the basic parameters.

        "outputType": "block",
        "bodyType": "none",

I also send you a direct email in case you need more information.

Cheers,
Sax

32

I’ve noticed the following Forge specific issues:

  1. Forge macros do not yet seem to support icons - assuming that’s a Forge platform concern, I’ve filed it as Missing icon support for macros (FRGE-211)
  2. Forge macros do not yet support categories either and are only appended to the ‘All’ category - given categories are about to change, I’ve refrained from filing a dedicated issue until the new approach is settled
33

Hi @PhilipFeldmann @TomHarris @lfcgomes - the issue with the edit pencil button not showing is now fixed and in prod. Please let me know if you’re still having issues.

2 Likes
34

Hi @BobBergman @jeff @TureHoefner - the issue with the plain text macro not falling back to the old config is now fixed and should be in prod. Let me know if you have any issues.

2 Likes
35

Just FYI you might need to do a hard refresh before you get the new changes.

36

Hi @sax,

It’s happening because Balsamiq Wireframes is defining a required parameter but doesn’t provide any value for it during insertion.

55%20pm
55%20pm1282×652 48.9 KB

We created an internal issue and working on the fix.

37

Hi @rifat,
As far as I remember that was the trick suggested in order to force the launch of the macro editor.

Glad that you are working on fixing it, let me know if we can help on the process.

38

@JonnoKatahanas, we are evaluating the possibility to use the new contextual configurator in our Balsamiq Wireframes app.
From our analysis in order to migrate to the new macro editor we are lacking the possibility to dynamically fill the values of an enum parameter (i.e. at the moment the macro allow the user to select the screen to show in the macro, and the number of screens is dynamically inferred by the structure of the project).
Do you have any solution for this scenario?

1 Like
39

I can see the pencil now :slight_smile: Thanks @JonnoKatahanas!

40

Hi @JonnoKatahanas,

We have a macro which is an inline plain text. Last week when I had tested out I was getting the new config panel on right. But today it seems to have reverted back to the old config experience.

Am I experiencing the “fallback to the old config experience” on my instance?

Cheers
Ajay