<!-- 
RSS generated by JIRA (9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b) at Mon Feb 12 06:18:06 CET 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Magnolia - Issue tracker</title>
    <link>https://jira.magnolia-cms.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-uk</language>    <build-info>
        <version>9.4.2</version>
        <build-number>940002</build-number>
        <build-date>19-01-2023</build-date>
    </build-info>


<item>
            <title>[PAGES-352] Provide endpoint for template annotations for SPA rendering</title>
                <link>https://jira.magnolia-cms.com/browse/PAGES-352</link>
                <project id="12087" key="PAGES">Magnolia pages module</project>
                    <description>&lt;p&gt;Timebox for investigation: &lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;How to pass the data/annotations? Does not necessarily have to REST&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&amp;#8212;&lt;/p&gt;

&lt;p&gt;There are many new tickets being created that relate to the html annotations in the page that are then used by the page editor. A part of resolving those tickets will involve changing the frontend-helpers library to change the annotation code to add some aspect that is present in the original server-side annotation creattion code.&lt;/p&gt;

&lt;p&gt;In the development of the Visual SPA Editor feature there was a choice to be made about how the annotations should be added with the frontend helpers. It was decided to re-implement the annotation creation in the frontend helpers, rather then to retrieve the annotations from the server.&lt;/p&gt;

&lt;p&gt;Based on these new tickets, and the realization that new modules (live copy, abtesting, etc) can impact the annotations, we should reassess that decision and see if there is a better approach such that we won&apos;t have to continuously change the frontend helpers library to accomodate new features being added to Magnolia on an ongoing basis.&lt;/p&gt;

&lt;p&gt;Please see linked &quot;caused by&quot; tickets to see issues that &lt;b&gt;might&lt;/b&gt; be related to this topic.&lt;/p&gt;</description>
                <environment></environment>
        <key id="89874">PAGES-352</key>
            <summary>Provide endpoint for template annotations for SPA rendering</summary>
                <type id="2" iconUrl="https://jira.magnolia-cms.com/secure/viewavatar?size=xsmall&amp;avatarId=10891&amp;avatarType=issuetype">New Feature</type>
                                            <priority id="3" iconUrl="https://jira.magnolia-cms.com/images/icons/priorities/major.svg">Major</priority>
                        <status id="6" iconUrl="https://jira.magnolia-cms.com/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="rsiska">Robert &#352;i&#353;ka</assignee>
                                    <reporter username="czimmermann">Christopher Zimmermann</reporter>
                        <labels>
                    </labels>
                <created>Wed, 26 Aug 2020 14:44:05 +0200</created>
                <updated>Wed, 7 Feb 2024 14:20:43 +0100</updated>
                            <resolved>Fri, 11 Dec 2020 13:13:52 +0100</resolved>
                                                    <fixVersion>6.2.5</fixVersion>
                                        <due></due>
                            <votes>2</votes>
                                    <watches>7</watches>
                                                    <progress percentage="100">
                                    <originalProgress>
                                                    <row percentage="0" backgroundColor="#89afd7"/>
                                                    <row percentage="100" backgroundColor="transparent"/>
                                            </originalProgress>
                                                    <currentProgress>
                                                    <row percentage="100" backgroundColor="#51a825"/>
                                                    <row percentage="0" backgroundColor="#ec8e00"/>
                                            </currentProgress>
                            </progress>
                                    <aggregateprogress percentage="100">
                                    <originalProgress>
                                                    <row percentage="0" backgroundColor="#89afd7"/>
                                                    <row percentage="100" backgroundColor="transparent"/>
                                            </originalProgress>
                                                    <currentProgress>
                                                    <row percentage="100" backgroundColor="#51a825"/>
                                                    <row percentage="0" backgroundColor="#ec8e00"/>
                                            </currentProgress>
                            </aggregateprogress>
                                            <timeestimate seconds="0">0d</timeestimate>
                            <timespent seconds="323100">11d 1.75h</timespent>
                                <comments>
                            <comment id="230367" author="bstaryga" created="Fri, 28 Aug 2020 14:03:44 +0200"  >&lt;p&gt;I am raising two hands for moving comment creation to server side.&lt;br/&gt;
The reason is not to get rid of template-annotation - this is only a nice side effect.&lt;br/&gt;
I have two resons:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Every prop used in green bars needs to be explicitly added to template-anotation lib. We already had to add the edit for dialog. Ecommerce headless demo is using patched version cause we had to add live copy props there. Personalization - not supported, noComponent - not supported, disabled - not supported (some more that we missed too, not supported?). Since we already have the nice piece of code that does all that comment buidling (used in freemarker), it is silly to try to rebuild it on JS side. Not only they are not kept in sync, we repeat the same functionality twice. Not to mention clients projects that add some extra stuff to green bars, they all would had to patch template annotation lib. So we close this route for any dev team who want to extend Magnolia without extra hustle.&lt;/li&gt;
	&lt;li&gt;We force extra lines of code on final budle size. This is not plenty, but if we can save few kb on js size we should do it.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Things like live copy or personalizations are bread and butter of every single sales demo we have right now, using patched code is not ideal &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.magnolia-cms.com/images/icons/emoticons/sad.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                            <comment id="231660" author="czimmermann" created="Wed, 9 Sep 2020 09:10:14 +0200"  >&lt;p&gt;Re: &quot;set the javascript object with all annotations into the page&quot;. At some points I found it helpful to be able to do some debugging of the green-bar creation directly on the React dev-server, which is only possible with it as a REST API. I guess a change like that would also &quot;break the contract&quot; and devs would need to update their projects, so it would necessitate a new major version, which would be nice to avoid.&lt;/p&gt;</comment>
                            <comment id="231665" author="bstaryga" created="Wed, 9 Sep 2020 09:34:36 +0200"  >&lt;p&gt;+1 to what &lt;a href=&quot;https://jira.magnolia-cms.com/secure/ViewProfile.jspa?name=czimmermann&quot; class=&quot;user-hover&quot; rel=&quot;czimmermann&quot;&gt;czimmermann&lt;/a&gt; says. Leave REST, it&apos;s not overhead, and it still leaves the ability for geeky projects to do some previews with e.g. some extra marking of components etc.&lt;br/&gt;
simply making rest return: e.g.&lt;br/&gt;
[ ...,&lt;br/&gt;
  {&lt;br/&gt;
    PATH_TO_COMP: &lt;/p&gt;
{
      open: OPEN_COMMENT_STRING,
      close: CLOSE_COMMENT_STRING
   }
&lt;p&gt;},&lt;br/&gt;
...]&lt;br/&gt;
will do the trick.&lt;/p&gt;</comment>
                            <comment id="235220" author="canh.nguyen" created="Mon, 5 Oct 2020 10:09:42 +0200"  >&lt;p&gt;&lt;a href=&quot;https://jira.magnolia-cms.com/secure/ViewProfile.jspa?name=mdrapela&quot; class=&quot;user-hover&quot; rel=&quot;mdrapela&quot;&gt;mdrapela&lt;/a&gt;&#160;for updating the document:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;The new endpoint is&#160;&lt;b&gt;/.rest/template-annotations/v1/&lt;/b&gt;&lt;/li&gt;
	&lt;li&gt;We need to add&#160;&lt;b&gt;mgnlPreview=false&lt;/b&gt; to the URL to make it work because the &lt;b&gt;RenderEngine&lt;/b&gt; will check this param to render freemarker templates. &lt;b&gt;mgnlPreview&lt;/b&gt; is true by default if we omit it.&lt;/li&gt;
	&lt;li&gt;Components need hardcode template scripts to be rendered, so we have to add following line to component definitions&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
class: info.magnolia.rendering.spa.renderer.SpaTemplateAnnotationRenderableDefinition
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="235233" author="czimmermann" created="Mon, 5 Oct 2020 10:35:10 +0200"  >&lt;p&gt;&lt;a href=&quot;https://jira.magnolia-cms.com/secure/ViewProfile.jspa?name=canh.nguyen&quot; class=&quot;user-hover&quot; rel=&quot;canh.nguyen&quot;&gt;canh.nguyen&lt;/a&gt;&#160;is there any way we can implement this so that developer does not have to add&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
class: info.magnolia.rendering.spa.renderer.SpaTemplateAnnotationRenderableDefinition
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;to every component definition? If so - would there be additional &quot;cost&quot; for us in additional effort now and maintenance?&lt;/p&gt;



&lt;p&gt;For one, we want the definitions as simple as possible. Additionally, this will be kind of intimidating for some frontend developers.&lt;/p&gt;</comment>
                            <comment id="235251" author="bstaryga" created="Mon, 5 Oct 2020 11:15:16 +0200"  >&lt;p&gt;&lt;a href=&quot;https://jira.magnolia-cms.com/secure/ViewProfile.jspa?name=canh.nguyen&quot; class=&quot;user-hover&quot; rel=&quot;canh.nguyen&quot;&gt;canh.nguyen&lt;/a&gt; +1 to what &lt;a href=&quot;https://jira.magnolia-cms.com/secure/ViewProfile.jspa?name=czimmermann&quot; class=&quot;user-hover&quot; rel=&quot;czimmermann&quot;&gt;czimmermann&lt;/a&gt; says. Big +1.&lt;/p&gt;</comment>
                            <comment id="235391" author="canh.nguyen" created="Tue, 6 Oct 2020 08:43:16 +0200"  >&lt;p&gt;&lt;a href=&quot;https://jira.magnolia-cms.com/secure/ViewProfile.jspa?name=czimmermann&quot; class=&quot;user-hover&quot; rel=&quot;czimmermann&quot;&gt;czimmermann&lt;/a&gt;&#160;I guess we can omit the class by implementing it like PersonalizationTemplateDefinition. But there is a problem that if I extend&#160;PersonalizationTemplateDefinition class, pages module will require personalization module (I&apos;ve not check dependency loop yet). If we don&apos;t extend&#160;PersonalizationTemplateDefinition class, we will lose that functionality.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.magnolia-cms.com/secure/ViewProfile.jspa?name=mgeljic&quot; class=&quot;user-hover&quot; rel=&quot;mgeljic&quot;&gt;mgeljic&lt;/a&gt;&#160;and &lt;a href=&quot;https://jira.magnolia-cms.com/secure/ViewProfile.jspa?name=apchelintcev&quot; class=&quot;user-hover&quot; rel=&quot;apchelintcev&quot;&gt;apchelintcev&lt;/a&gt;&#160;could you please give me some advice for this issue?&lt;/p&gt;</comment>
                            <comment id="235416" author="mgeljic" created="Tue, 6 Oct 2020 09:42:26 +0200"  >&lt;p&gt;Re: personalization dep in pages, that would be a no-go but there would be various ways to invert that dependency.&lt;br/&gt;
As discussed, let&apos;s review the general approach here.&lt;/p&gt;</comment>
                            <comment id="241321" author="rsiska" created="Tue, 24 Nov 2020 16:33:08 +0100"  >&lt;p&gt;Update for docu:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;The new endpoint is&#160;&lt;b&gt;/.rest/template-annotations/v1/&lt;/b&gt;&lt;/li&gt;
	&lt;li&gt;**No template definitions need to be changed.&lt;/li&gt;
	&lt;li&gt;Page template def. still needs to declare &lt;tt&gt;renderType: spa&lt;/tt&gt;&#160;and &lt;tt&gt;class:&#160;info.magnolia.rendering.spa.renderer.SpaRenderableDefinition&lt;/tt&gt;&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="241324" author="bstaryga" created="Tue, 24 Nov 2020 16:56:11 +0100"  >&lt;p&gt;Quick question, do I see correctly that I would have to change the `class` and the endpoint to use newer approach?&lt;br/&gt;
How would it look on fe side?&lt;/p&gt;

&lt;p&gt;Is there a possibility that this whole change is more graceful and handled behind the scenes, so the same class endpoint etc, all stays the same, and handling is handled in fe editor libs? Eg. endpoint could return some flag and fe libs would process it accordingly, and we could give a grace period for users to migrate to latest and then remove old code.&lt;/p&gt;

&lt;p&gt;I just hate to ask again our partners/clients that if they wanna use something newer they need to modify their code again... (i know they will have to update fe libs, but we would at least save them from need to update yaml. small gesture but nice )&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.magnolia-cms.com/secure/ViewProfile.jspa?name=czimmermann&quot; class=&quot;user-hover&quot; rel=&quot;czimmermann&quot;&gt;czimmermann&lt;/a&gt; what do you think?&lt;/p&gt;

&lt;p&gt;Or we communicate it as &lt;b&gt;/templateDefinition/v2&lt;/b&gt;, after all this is why we have versioning i guess &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.magnolia-cms.com/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                            <comment id="241329" author="rsiska" created="Tue, 24 Nov 2020 17:08:53 +0100"  >&lt;p&gt;The class stays the same as it was before. And it needs to be there because it defines jsPaths and cssPaths attributes.&lt;/p&gt;

&lt;p&gt;&lt;cite&gt;Or we communicate it as* /templateDefinition/v2*, after all this is why we have versioning i guess&lt;/cite&gt;&lt;/p&gt;

&lt;p&gt;That&apos;s a good point, but I wanted to make it obvious that the endpoint has different purpose - it returns annotations rather than template definitions.&#160;&lt;/p&gt;

&lt;p&gt;And it only needs to be changed on one place, so I reckoned it&apos;s not such a big deal. wdyt?&lt;/p&gt;

&lt;p&gt;The old definition endpoint still works, by the way, so nothing should break after update.&lt;/p&gt;</comment>
                            <comment id="241331" author="czimmermann" created="Tue, 24 Nov 2020 17:12:28 +0100"  >&lt;p&gt;I just checked one of my code examples - there in the page definition i have:&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;class: info.magnolia.rendering.spa.renderer.SpaRenderableDefinition&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;Can I still use that &lt;a href=&quot;https://jira.magnolia-cms.com/secure/ViewProfile.jspa?name=rsiska&quot; class=&quot;user-hover&quot; rel=&quot;rsiska&quot;&gt;rsiska&lt;/a&gt;? Because you mention a different one in above comment.&lt;/p&gt;</comment>
                            <comment id="241332" author="bstaryga" created="Tue, 24 Nov 2020 17:13:17 +0100"  >&lt;p&gt;hmmm the class I have in current ones is:&lt;br/&gt;
class: info.magnolia.rendering.spa.renderer.SpaRenderableDefinition&lt;br/&gt;
you say new one is:&lt;br/&gt;
class: info.magnolia.rendering.spa.renderer.ConfiguredSpaRenderableDefinition&lt;br/&gt;
is that some new class from previous release I missed? LOL &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.magnolia-cms.com/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;

&lt;p&gt;Then only question I have is, why not: /templateDefinition/v2? Why completely new endpoint?&lt;/p&gt;</comment>
                            <comment id="241335" author="czimmermann" created="Tue, 24 Nov 2020 17:19:54 +0100"  >&lt;p&gt;I think the endpoint renaming is reasonable since it really does return different information (not just definitions anymore - YAY). (And same amount of work for the FE developer either way.)&lt;/p&gt;</comment>
                            <comment id="241336" author="rsiska" created="Tue, 24 Nov 2020 17:20:53 +0100"  >&lt;p&gt;Ah, you&apos;re right. You can (and should) use&#160;info.magnolia.rendering.spa.renderer.SpaRenderableDefinition.&lt;/p&gt;



&lt;p&gt;&lt;cite&gt;Why completely new endpoint&lt;/cite&gt;?&lt;br/&gt;
I edited my previous comment. TLDR: because it doesn&apos;t return template definitions anymore.&lt;/p&gt;</comment>
                            <comment id="241372" author="bstaryga" created="Wed, 25 Nov 2020 09:30:02 +0100"  >&lt;p&gt; &lt;a href=&quot;https://jira.magnolia-cms.com/secure/ViewProfile.jspa?name=rsiska&quot; class=&quot;user-hover&quot; rel=&quot;rsiska&quot;&gt;rsiska&lt;/a&gt;&lt;br/&gt;
&lt;b&gt;Regarding the endpoint name&lt;/b&gt;&lt;br/&gt;
Fair enough &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.magnolia-cms.com/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;br/&gt;
Just to shed some light why I&apos;m writing what I am writing is cause for every developer I came across that had to implement that bit in FE this is some arbitrary code that needs to be added (in 90% cases copy-pasted from our examples) so we have green bars.&lt;br/&gt;
There is either very small understanding what is being fetched there or majority has 0 understanding of it at all.&lt;br/&gt;
Anyway make sense what you  are saying &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.magnolia-cms.com/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;

&lt;p&gt;So question more visual then:&lt;br/&gt;
Old one is called: &lt;b&gt;templateDefinition&lt;/b&gt; and new one &lt;b&gt;template-annotations&lt;/b&gt;. What is the preferred way of naming endpoints in  PD? Camel case or dashes?&lt;/p&gt;

&lt;p&gt;Would you mind sharing here example response from that endpoint here please?&lt;/p&gt;</comment>
                            <comment id="241504" author="canh.nguyen" created="Thu, 26 Nov 2020 04:23:03 +0100"  >&lt;p&gt;&lt;a href=&quot;https://jira.magnolia-cms.com/secure/ViewProfile.jspa?name=bstaryga&quot; class=&quot;user-hover&quot; rel=&quot;bstaryga&quot;&gt;bstaryga&lt;/a&gt;&#160;we&apos;ve changed to &lt;b&gt;template-definitions&lt;/b&gt; long ago, but we continue support&#160;&lt;b&gt;templateDefinition&lt;/b&gt;&#160;for backward compatibility.&lt;/p&gt;</comment>
                            <comment id="241541" author="bstaryga" created="Thu, 26 Nov 2020 10:44:05 +0100"  >&lt;p&gt;&lt;a href=&quot;https://jira.magnolia-cms.com/secure/ViewProfile.jspa?name=canh.nguyen&quot; class=&quot;user-hover&quot; rel=&quot;canh.nguyen&quot;&gt;canh.nguyen&lt;/a&gt; hehehe, we missed it all at FE team then &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.magnolia-cms.com/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;br/&gt;
I shall update all our materials accordingly then.&lt;/p&gt;</comment>
                            <comment id="241814" author="czimmermann" created="Mon, 30 Nov 2020 10:16:45 +0100"  >&lt;p&gt;Fix version is 6.2.5, Magnolia version is 6.2.6. What version is this in? Was it shipped with 6.2.5?&lt;/p&gt;</comment>
                            <comment id="241962" author="rsiska" created="Tue, 1 Dec 2020 09:58:31 +0100"  >&lt;p&gt;It was reverted in the final QA and because it is the only change in pages 6.2.5 so far, the module wasn&apos;t released. Magnolia 6.2.5 was released with pages 6.2.4.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10040">
                    <name>causality</name>
                                            <outwardlinks description="caused by">
                                        <issuelink>
            <issuekey id="89236">MGNLFE-67</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="89128">MGNLFE-65</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="89129">MGNLFE-66</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="89131">MGNLFE-68</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="89860">MGNLFE-70</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="89132">MGNLFE-64</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="88111">MGNLFE-57</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="88228">MGNLFE-58</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="88923">MGNLFE-61</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="89038">MGNLFE-62</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is causing">
                                        <issuelink>
            <issuekey id="91394">PAGES-356</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10020">
                    <name>dependency</name>
                                                                <inwardlinks description="is depended upon by">
                                        <issuelink>
            <issuekey id="90848">MGNLFE-77</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10010">
                    <name>relation</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="89793">MGNLFE-74</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_14166" key="com.okapya.jira.checklist:checklist">
                        <customfieldname>Acceptance criteria</customfieldname>
                        <customfieldvalues>
                            
        <checklist>
        <![CDATA[
                            




                
                                    <div class="o-completion" style="display: flex; flex-shrink: 0;"><span  class="aui-lozenge aui-lozenge-complete" style="font-size: 12px; font-weight: normal; display: flex; flex-direction: row; align-items: center;" ><span style="padding-right: 4px; vertical-align: middle;"><svg width="15" height="15" viewBox="0 0 15 15" xmlns="http://www.w3.org/2000/svg" fill="white"><path clip-rule="evenodd" d="m10.41037,3.42544l-7.86501,0c-0.72395,0 -1.31084,0.58688 -1.31084,1.31084l0,7.86508c0,0.7239 0.58689,1.3108 1.31084,1.3108l7.86501,0c0.724,0 1.3109,-0.5869 1.3109,-1.3108l0,-7.86508c0,-0.72396 -0.5869,-1.31084 -1.3109,-1.31084zm-7.86501,-0.65542c-1.08593,0 -1.96626,0.88032 -1.96626,1.96626l0,7.86508c0,1.0859 0.88033,1.9662 1.96626,1.9662l7.86501,0c1.086,0 1.9663,-0.8803 1.9663,-1.9662l0,-7.86508c0,-1.08594 -0.8803,-1.96626 -1.9663,-1.96626l-7.86501,0z" fill-rule="evenodd"/><path d="m5.09049,10.18526l-1.82767,-1.82766l-0.78479,0.78479l2.61246,2.61246l5.38758,-5.38754l-0.78483,-0.78479l-4.60275,4.60274z"/></svg></span><span>Empty</span></span></div>
                        ]]>
    </checklist>


                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10111" key="com.atlassian.jira.toolkit:reporterdomain">
                        <customfieldname>Company</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>magnolia-cms.com</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10031" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 27 Aug 2020 03:41:08 +0200</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_12730" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_14151" key="com.atlassian.jira.toolkit:message">
                        <customfieldname>Docu info</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_12130" key="com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes">
                        <customfieldname>Documentation update required</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="13300"><![CDATA[Yes]]></customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10246" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>PAGES-190</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10061" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comm is not jira-dev</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>false</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10071" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last participant</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>mdrapela</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_13136" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            3 years, 10 weeks, 5 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10020" key="com.atlassian.jira.toolkit:attachments">
                        <customfieldname>Number of attachments</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10150" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname>Number of comments</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>20.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10011" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>bstaryga</customfieldvalue>
            <customfieldvalue>canh.nguyen</customfieldvalue>
            <customfieldvalue>czimmermann</customfieldvalue>
            <customfieldvalue>mgeljic</customfieldvalue>
            <customfieldvalue>rsiska</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_10833" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|y02xkl:i</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10244" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10245" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="1273">HL &amp; LD 12</customfieldvalue>
    <customfieldvalue id="1283">HL &amp; LD 13</customfieldvalue>
    <customfieldvalue id="1299">HL &amp; LD 14</customfieldvalue>
    <customfieldvalue id="1312">HL &amp; LD 15</customfieldvalue>
    <customfieldvalue id="1323">HL &amp; LD 16</customfieldvalue>
    <customfieldvalue id="1331">HL &amp; LD 17</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10242" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>13.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_14145" key="com.intenso.jira.issue-templates:issue-templates-customfield">
                        <customfieldname>Template</customfieldname>
                        <customfieldvalues>
                            


                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_15131" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Time in Discovery</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10032" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_13933" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Urgency (resolution)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="15724"><![CDATA[Normal]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>