<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:04:42 UTC 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 add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[FOLIO-293] Recommendations on when to use Jira vs. Discuss vs. Slack etc.</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-293</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;Some people will be unsure how to decide whether to post a question or problem they have to Jira, Discuss, Slack, etc.  Could we develop some recommendations or guidelines to offer them, and post these both in the communication areas and on the developer website?&lt;/p&gt;</description>
                <environment></environment>
        <key id="80011">FOLIO-293</key>
            <summary>Recommendations on when to use Jira vs. Discuss vs. Slack etc.</summary>
                <type id="10002" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium">New Feature</type>
                                            <priority id="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="61cd0ca0bce5e00069e98be7">David Crossley</assignee>
                                                                <reporter accountid="70121:8d96963c-ce4c-478d-9023-2de35bc14b67">Nassib Nassar</reporter>
                                    <labels>
                    </labels>
                <created>Fri, 2 Sep 2016 17:05:07 +0000</created>
                <updated>Mon, 12 Nov 2018 14:23:14 +0000</updated>
                            <resolved>Mon, 17 Oct 2016 06:00:25 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                    <timespent seconds="5400">1 hour, 30 minutes</timespent>
                                <comments>
                                                            <comment id="191182" author="70121:8d96963c-ce4c-478d-9023-2de35bc14b67" created="Fri, 2 Sep 2016 17:26:39 +0000"  >&lt;p&gt;I think usually Jira would be used for reporting very specific bugs, problems, or feature requests, while the discussion areas (Discuss/Slack) would be used for open-ended questions or comments.&lt;/p&gt;</comment>
                                                            <comment id="191184" author="5ced27478b03050f27825a93" created="Fri, 2 Sep 2016 17:48:26 +0000"  >&lt;p&gt;I agree &amp;#8211; that makes sense.  And, of course, one can link back and forth between the two (if something starts as a Discuss topic and turns into an Issue).&lt;/p&gt;</comment>
                                                            <comment id="191186" author="61cd0ca0bce5e00069e98be7" created="Tue, 6 Sep 2016 09:11:06 +0000"  >&lt;p&gt;Commenced at branch &lt;a href=&quot;https://github.com/folio-org/folio-org.github.io/tree/folio-293-which-forum&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/folio-org.github.io/tree/folio-293-which-forum&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Ready for an initial look to ensure on the right track.&lt;/p&gt;

&lt;p&gt;I am not sure how to balance this with:&lt;br/&gt;
&lt;a href=&quot;https://folio-org.atlassian.net/wiki/display/COMMUNITY/FOLIO+Communication+Spaces&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/wiki/display/COMMUNITY/FOLIO+Communication+Spaces&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="191188" author="63e2a2771b13d42998e4e706" created="Wed, 7 Sep 2016 09:35:09 +0000"  >&lt;p&gt;Hi David, thank you for putting this draft together.&lt;/p&gt;

&lt;p&gt;I think this is a good start and it is what I had in mind when I asked the question. I&apos;m not an expert in how to do this (I filed my first ever open source issue yesterday), so I don&apos;t think I&apos;m well placed to comment on how the process is intended to operate.&lt;/p&gt;

&lt;p&gt;I think this is a complementary subset of the general guidance, and I think the link which you included is sufficient to reference that.&lt;/p&gt;

&lt;p&gt;With that in mind though, I think it&apos;s ok to omit the Slack section, if we think that it doesn&apos;t play much of a role in raising issues.&lt;/p&gt;</comment>
                                                            <comment id="191190" author="61cd0ca0bce5e00069e98be7" created="Thu, 8 Sep 2016 01:18:46 +0000"  >&lt;p&gt;Thanks for making time to comment.&lt;/p&gt;

&lt;p&gt;This issue&apos;s Description says to also put these guidelines on the Wiki. I am not sure how that can be done. Perhaps the Wiki could just link to this dev.folio.org page for these developer guidelines.&lt;/p&gt;

&lt;p&gt;I do think that Slack is relevant, just do not yet know what to recommend.&lt;/p&gt;</comment>
                                                            <comment id="191191" author="70121:8d96963c-ce4c-478d-9023-2de35bc14b67" created="Thu, 8 Sep 2016 03:00:48 +0000"  >&lt;p&gt;David, thanks, I think this is a really good start.&lt;/p&gt;

&lt;p&gt;My thought was that you might coordinate with Peter who knows all about the wiki.&lt;/p&gt;

&lt;p&gt;Yesterday we made some changes to the Discuss vs. Slack part of this decision process; Peter can provide you the latest document on it.&lt;/p&gt;</comment>
                                                            <comment id="191193" author="5ced27478b03050f27825a93" created="Thu, 8 Sep 2016 16:32:11 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt; &#8211; I integrated a lot of your content into &lt;a href=&quot;https://folio-org.atlassian.net/wiki/display/COMMUNITY/FOLIO+Communication+Spaces&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/wiki/display/COMMUNITY/FOLIO+Communication+Spaces&lt;/a&gt; (thank you!).  Unless we have something specific to say to developers about the tools (for instance, any developer-specific needs, requirements, or guidance), I think we can drop this page and point to the one on the wiki instead.&lt;/p&gt;</comment>
                                                            <comment id="191195" author="5ced27478b03050f27825a93" created="Thu, 8 Sep 2016 19:14:52 +0000"  >&lt;p&gt;Added a &lt;a href=&quot;https://github.com/folio-org/folio-org.github.io/pull/12/commits/0f51218d579a2a886d78c8fbf99295e1c7154573&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;commit&lt;/a&gt; on the branch that has some changes, but I&apos;m of the opinion that we can point to the broader community&apos;s &lt;a href=&quot;https://folio-org.atlassian.net/wiki/display/COMMUNITY/FOLIO+Communication+Spaces&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;FOLIO Communication Spaces&lt;/a&gt; page.&lt;/p&gt;</comment>
                                                            <comment id="191197" author="61cd0ca0bce5e00069e98be7" created="Fri, 9 Sep 2016 01:36:22 +0000"  >&lt;p&gt;Peter, that is a great evolution of content. The primary/secondary was the key.&lt;/p&gt;

&lt;p&gt;Reviewing that Wiki page, i do see a few minor typos.&lt;/p&gt;

&lt;p&gt;However, there is something major. Some of the text had links to other stuff on dev.folio.org and they were relative links. So now busted on the Wiki. These will need absolute links.&lt;/p&gt;

&lt;p&gt;In one case it is a link to a document in-preparation (&quot;guide-issues&quot;) on that branch (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-298&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-298&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Guidelines for creating issues in Jira&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            FOLIO-298
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 about JIRA guidelines). So need to remove the link on the Wiki. That is also evolving through 
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;FOLIO-304&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-304&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;document Jira process/model used across FOLIO project&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-304
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-complete jira-macro-single-issue-export-pdf&quot;&gt;Open&lt;/span&gt;
            &lt;/span&gt;
. So we can link again when ready.&lt;/p&gt;

&lt;p&gt;(Ah, reinforced a lesson. Doing two things on the same branch. Erk.)&lt;/p&gt;</comment>
                                                            <comment id="191199" author="61cd0ca0bce5e00069e98be7" created="Fri, 9 Sep 2016 04:08:27 +0000"  >&lt;p&gt;Published an update via &lt;a href=&quot;https://github.com/folio-org/folio-org.github.io/pull/13&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;pull/13&lt;/a&gt;&lt;br/&gt;
essentially linking to that enhanced Wiki page.&lt;/p&gt;

&lt;p&gt;We can later add specific developer notes as needed.&lt;/p&gt;</comment>
                                                            <comment id="191200" author="5ced27478b03050f27825a93" created="Fri, 9 Sep 2016 12:30:09 +0000"  >&lt;p&gt;Thanks &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt;.  I&apos;ve updated the wiki to correct the links back to dev.folio.org.  (Sorry about missing that in copying-and-pasting from the rendered Markdown.)  I think we can close this issue.&lt;/p&gt;</comment>
                                                            <comment id="191202" author="61cd0ca0bce5e00069e98be7" created="Sat, 10 Sep 2016 06:47:51 +0000"  >&lt;p&gt;We had a direct discussion in Slack: We need to have all developer-related information gathered at dev.folio.org and the full context is good there. The overlap with the Wiki is fine. This is for a different audience.&lt;/p&gt;

&lt;p&gt;So will continue with the branch folio-293-which-forum.&lt;/p&gt;</comment>
                                                            <comment id="191204" author="61cd0ca0bce5e00069e98be7" created="Sun, 11 Sep 2016 12:10:43 +0000"  >&lt;p&gt;Ready with &lt;a href=&quot;https://github.com/folio-org/folio-org.github.io/pull/15&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;pull/15&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="191205" author="61cd0ca0bce5e00069e98be7" created="Sun, 11 Sep 2016 23:21:26 +0000"  >&lt;p&gt;That is merged and published now.&lt;/p&gt;

&lt;p&gt;So finished this first round.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="80013">FOLIO-298</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzxegn:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Fri, 2 Sep 2016 17:48:26 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>