<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Taskrd blog</title>

    <link href="http://blog.taskrd.com/atom.xml" rel="self"/>
    <link href="http://blog.taskrd.com"/>

    <updated>2012-07-25T09:18:41+02:00</updated>

    <id>http://blog.taskrd.com</id>
    <author>
        <name>Jaime Gil de Sagredo</name>
    </author>

    
    <entry>
        <title>Taskrd, a Bitbucket issues dashboard</title>
        <link href="http://blog.taskrd.com/2012/07/11/taskrd-bitbucket-issues-dashboard.html"/>
        <updated>2012-07-11T00:00:00+02:00</updated>
        <id>http://blog.taskrd.com/2012/07/11/taskrd-bitbucket-issues-dashboard</id>
        <content type="html">&lt;p&gt;Today I&amp;#8217;m very glad to introduce you the project in which I&amp;#8217;ve been working on the past few weeks. This is &lt;a href='http://taskrd.com'&gt;Taskrd&lt;/a&gt;, a web dashboard for your &lt;a href='https://bitbucket.org'&gt;Bitbucket.org&lt;/a&gt; repositories issues.&lt;/p&gt;
&lt;img alt='Taskrd logo' src='/images/taskrd.png' /&gt;
&lt;h2 id='an_issues_dashboard'&gt;An issues dashboard&lt;/h2&gt;

&lt;p&gt;I&amp;#8217;m using Bitbucket for a while to host my projects source code repositories and managing their issues. When I&amp;#8217;m working on a project, I usually add bugs or pending tasks to another projects to solve them when I coming back to one of these projects, and then I continue working on my current project.&lt;/p&gt;

&lt;p&gt;This approach works really well because lets me remain focused on my current work, and later, when I&amp;#8217;ve finished, I can go to my repositories issues and see which could be my next move. But there is a problem with this approach. According to the number of repositories increases, it becomes more and more difficult to remember which of them has pending issues.&lt;/p&gt;

&lt;p&gt;Here is where Taskrd comes into play.&lt;/p&gt;

&lt;h2 id='displaying_pending_issues'&gt;Displaying pending issues&lt;/h2&gt;

&lt;p&gt;At this point I needed to see my pending issues for each repository at a glance, so the first screen you will see when login into Taskrd will be a list with all of your repositories with at least one pending issue, and their issues.&lt;/p&gt;
&lt;img alt='Taskrd home dashboard displaying all repositories' src='/images/all-repositories.png' /&gt;
&lt;p&gt;Additionally, the issues are sorted by priority. Blocking and critical issues are displayed in the top and have different colors to highlight them from trivial and minor issues. In this way you can see which issues are more important and start working on them quickly.&lt;/p&gt;

&lt;p&gt;Also you can navigate to a specific repository to see only this subset of all your pending issues.&lt;/p&gt;

&lt;h2 id='adding_new_issues'&gt;Adding new issues&lt;/h2&gt;

&lt;p&gt;Watch all your pending issues can be a great tool, but many times you remember an unreported bug or you think you need a new feature for your project, so it&amp;#8217;s also possible to add new issues to a repository from here.&lt;/p&gt;

&lt;p&gt;The only thing you need to add a new issue is to specify the issue title, priority and kind. This process is done in a faster and more intuitive way than doing it from Bitbucket.&lt;/p&gt;
&lt;img alt='Adding a new issue' src='/images/adding-new-issue.png' /&gt;
&lt;h2 id='access_with_your_bitbucket_account'&gt;Access with your Bitbucket account&lt;/h2&gt;

&lt;p&gt;Taskrd is built on top of the &lt;a href='https://api.bitbucket.org'&gt;Bitbucket REST API&lt;/a&gt; to access the user repositories, using OAuth to authorize the application and authenticate the user, so it is not necessary to register a new account in Taskrd. Only your Bitbucket account is needed!&lt;/p&gt;

&lt;h2 id='what_about_the_future'&gt;What about the future?&lt;/h2&gt;

&lt;p&gt;This is only the beginning, the first public beta to start sharing all of this work with others and getting feedback. I&amp;#8217;m working on more features including a better issues management, a better look and user experience and fixing some minor problems.&lt;/p&gt;

&lt;p&gt;Also I want to register Taskrd in the &lt;a href='https://marketplace.atlassian.com/codegeist'&gt;Codegeist&lt;/a&gt; to reach a higher number of potential users. And, why not, be the first Bitbucket add-on in the contest.&lt;/p&gt;

&lt;h2 id='final_words'&gt;Final words&lt;/h2&gt;

&lt;p&gt;You can get in touch with the project in &lt;a href='https://twitter.com/taskrd'&gt;Twitter&lt;/a&gt; and report issues and suggestions in the &lt;a href='https://bitbucket.org/jaimegildesagredo/taskrd-support/issues'&gt;issue tracker&lt;/a&gt;. All opinions are welcome, so feel free to leave a comment.&lt;/p&gt;

&lt;p&gt;Finally, I want to thank to the awesome Bitbucket.org team for their work, and encourage you to start using Taskrd and help making it better ;)&lt;/p&gt;</content>
    </entry>
    
</feed>
