<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jira on JOURNAL.ROBBI.MY</title><link>https://journal.robbi.my/tags/jira/</link><description>Recent content in Jira on JOURNAL.ROBBI.MY</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 26 Dec 2022 13:22:03 +0800</lastBuildDate><atom:link href="https://journal.robbi.my/tags/jira/index.xml" rel="self" type="application/rss+xml"/><item><title>How to write issues / bug report?</title><link>https://journal.robbi.my/posts/210606100700/</link><pubDate>Sun, 06 Jun 2021 22:07:00 +0800</pubDate><guid>https://journal.robbi.my/posts/210606100700/</guid><description>&lt;p&gt;To be honest, there are many articles written before on this very subject but I gonna write it based on what I learned and experienced working with european, asian company and my involvement with opensource and proprietary software. This 5 criteria helps you getting a clear report and getting fast response.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Stay cool&lt;/strong&gt; - Don’t expect all of your issue to be accepted and paid for (bug bounty?). You should report it ASAP if you found problems and collect all log, screenshot or any evidance to prove what you want to tell. You might missed something and the expertise such as developer may ask you more stuff and guide you how to get it, some won&amp;rsquo;t but please do stop youself from reporting.&lt;/p&gt;</description></item></channel></rss>