<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Managing App Development in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Managing-App-Development/m-p/1785470#M17416</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;Looking for suggestions / best practices around managing development of apps in Qlik Sense. It seems like the only way to manage development is to have multiple streams. That has become an issue because there's not a clear 'go to' folder where all gold / tip versions of an app may be located. If a team goes with a single 'main branch' stream then the issue becomes overload of apps in a single folder.&lt;/P&gt;&lt;P&gt;Ideally there would be an ability to create a folder structure within a stream for managing apps. As an example&amp;nbsp;&lt;/P&gt;&lt;P&gt;Main Branch / IT&lt;/P&gt;&lt;P&gt;Main Branch&amp;nbsp; / HR&lt;/P&gt;&lt;P&gt;Main Branch / Sales&lt;/P&gt;&lt;P&gt;Main Branch / Finance&amp;nbsp;&lt;/P&gt;&lt;P&gt;etc.&lt;/P&gt;&lt;P&gt;I'd appreciate any thoughts or examples of how other folks have worked through this.&lt;/P&gt;</description>
    <pubDate>Tue, 23 Feb 2021 20:01:48 GMT</pubDate>
    <dc:creator>derrydavis</dc:creator>
    <dc:date>2021-02-23T20:01:48Z</dc:date>
    <item>
      <title>Managing App Development</title>
      <link>https://community.qlik.com/t5/Management-Governance/Managing-App-Development/m-p/1785470#M17416</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;Looking for suggestions / best practices around managing development of apps in Qlik Sense. It seems like the only way to manage development is to have multiple streams. That has become an issue because there's not a clear 'go to' folder where all gold / tip versions of an app may be located. If a team goes with a single 'main branch' stream then the issue becomes overload of apps in a single folder.&lt;/P&gt;&lt;P&gt;Ideally there would be an ability to create a folder structure within a stream for managing apps. As an example&amp;nbsp;&lt;/P&gt;&lt;P&gt;Main Branch / IT&lt;/P&gt;&lt;P&gt;Main Branch&amp;nbsp; / HR&lt;/P&gt;&lt;P&gt;Main Branch / Sales&lt;/P&gt;&lt;P&gt;Main Branch / Finance&amp;nbsp;&lt;/P&gt;&lt;P&gt;etc.&lt;/P&gt;&lt;P&gt;I'd appreciate any thoughts or examples of how other folks have worked through this.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2021 20:01:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Managing-App-Development/m-p/1785470#M17416</guid>
      <dc:creator>derrydavis</dc:creator>
      <dc:date>2021-02-23T20:01:48Z</dc:date>
    </item>
    <item>
      <title>Re: Managing App Development</title>
      <link>https://community.qlik.com/t5/Management-Governance/Managing-App-Development/m-p/1799136#M19193</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;Unfortunately this is currently not possible in QSEoW. Here is an associated idea that you can vote on&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Suggest-an-Idea/Folders-in-your-own-workspace-and-streams/idi-p/1530082" target="_blank"&gt;https://community.qlik.com/t5/Suggest-an-Idea/Folders-in-your-own-workspace-and-streams/idi-p/1530082&lt;/A&gt;&lt;/P&gt;&lt;P&gt;There is also an interesting feedback provided by&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/14348"&gt;@Thomas_Hopp&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The best approach with the current capabilities is probably to use tags which then can be searched in the Qlik Sense hub.&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;</description>
      <pubDate>Tue, 13 Apr 2021 14:44:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Managing-App-Development/m-p/1799136#M19193</guid>
      <dc:creator>Bastien_Laugiero</dc:creator>
      <dc:date>2021-04-13T14:44:24Z</dc:date>
    </item>
  </channel>
</rss>

