Posts Tagged ‘plugins’

New Integrations in tinyPM v2.5.2

Marcin Niebudek,

With version 2.5 we’ve introduced plugins for activity history stream in tinyPM. Today we’re happy to let you know that three more plugins have been released along with tinyPM 2.5.2. You can now connect to Mercurial repositories both hosted on your own servers and those from Bitbucket as well as Git repositories from Github.

This means that now tinyPM history plugins list contains:

  • Mercurial (hg)
  • Bitbucket
  • Github
  • Subversion (SVN)
  • RSS/Atom Feeds

You will find more details about using the new plugins (as well as all other available in tinyPM) in our documentation, which has been updated recently at:

http://documentation.tinypm.com/display/DOC/Plugins

You’ve probably noticed that the list is missing Git repositories hosted outside of Github. That’s right, but the plugin is on the way :-) so stay tuned.

As always we want to thank our community users who provide fixes to the tinyPM translations (some of them are also included in v2.5.2). You all rock!

Please take a look at the full list of changes for v2.5.2 in the change log.

tinyPM v2.5 Released

Marcin Niebudek,

So here it is… tinyPM v2.5 is ready for download. This version brings two big features – release planning and SVN itegration. In fact the SVN integration is done through plugin which is the first implementation of history plugins API which we will hopefully be able to open for our community this year.

There is also one more thing which we wouldn’t be able to accomplish without a great work done by the community members. tinyPM gets 7 new translations and has now 13 language versions!

Release planning

We’ve introduced releases in tinyPM projects. They have two functions. First one is that they become markers dividing you planned parts of  backlog, so you can quickly see what’s going to be finished for which version of the product. These are those dark blue bars on the backlog screenshot.

In the other hand future releases give you additional place for unplanned stories. So now it’s possible to divide a large backlog into smaller chunks without planning to many iterations ahead (green boxes in the left column of a backlog).

tinyPM is now also able to forecast release dates based on the estimated effort of stories assigned to each release and an average velocity of your team. Releases can have also planned velocity value defined, which will be used to forecast dates and release performance indicators (similar to those already present on project dashboard) at the beginning of the project when average team velocity is unknown.

SVN Itegration / History Plugins

We’ve built the infrastructure for a new type of plugins (except for the sandbox connectors already present in tinyPM). Those plugins allow to connect to some sources like source code repositories or build servers and collect events (like code commits or build statuses) and put them into the tinyPM’s history timeline. Some of those plugins will also allow to bind those events with user stories.

Along with new API for history plugins we release the first implementation of such a plugin which is able to import code commit messages from Subversion repository and is also able to bind those commits (and changed files list) with stories. All you need to do is to put the user story id like #123 in the commit message and all commited files will be associated with a story having id #123.

You can read more about configuring this plugin in our documentation at:
http://documentation.tinypm.com/display/DOC/SVN+Plugin

Translations

One more time we want to thank all the tinyPM users who provided translations for their native languages. tinyPM v2.5 is release with the following new translations:

  • Chinese
  • Danish
  • Dutch
  • Russian
  • Spanish
  • Turkish
  • Ukrainian

All users are welcome to improve any of those translations or add new ones at:
http://support.tinypm.com/translate/languages.jsf

If you want to take a look at some of the new features, go to our on-line DEMO:
http://demo.tinypm.com

Full list of changes is always available at:
http://documentation.tinypm.com/display/DOC/Change+log

UserVoice suggestions become tinyPM user stories

Marcin Niebudek,

We’ve just release tinyPM 2.2.1 which adds new tinyPM connector for UserVoice. This plugin allows you to integrate your UserVoice forum with tinyPM sandbox and automatically import posted suggestions. When you’re ready you may convert them into stories.

Right now connector does not update suggestion statuses back in UserVoice forum, but we hope to handle that soon. So let’s take a look at how to configure new connector in tinyPM.

Connecting to your UserVoice forum with tinyPM

First thing you need to find is your forum URL. So simply go to your UserVoice page and go into your forum (if you have more of them). What you get in the address bar is the required forum URL.

tinyPM UserVoice feedback forum

After that choose Connector for UserVoice in tinyPM data source settings (projects list -> Project data sources) and set your forum URL.

Configuring tinyPM conenctor for UserVoice

That’s all you have to define. Now tinyPM will pool all new suggestions whenever they are posted to your UserVoice forum.

What else did we add in tinyPM 2.2.1?

  • defining more than one default task for your stories
  • defining estimated “time left” in the timesheet
  • Scrum-like iteration burndown chart based on “time left”
  • deleting more stories at once on backlog (new menu “Actions” for each iteration)
  • iterations are now always ordered by start and end dates
  • fixed “close iteration” problem when iteration positions are messed up
  • default iteration name pattern is now configurable in project settings
  • iteration number is editable again to be able to make “Iteration 0″ the first one and keep proper naming of subsequent iterations
  • added “Actions” menu for stories and sandbox items
  • editable user initials (no need to hack user names anymore)

We hope you will find all those changes helpful.

Connecting to JIRA and POP3 mailboxes with tinyPM connectors

Marcin Niebudek,

So you know already that tinyPM 2.2 have Sandbox with connectors that allow you to import items, issues, messages and ideas from different places. For a good start we equipped tinyPM with two connectors. One for getting issues from JIRA and one for importing e-mail messages sent to any POP3 mailbox. Now let’s have a look at how to configure them and use to populate your new Sandbox.

Connecting to JIRA

tinyPM uses JIRA API to import issues, but the API requires you to create a filter. So the first thing you need to do is to create one in your JIRA.

Creating JIRA filter for tinyPM

tinyPM will monitor any defined data source periodically so any newly reported issue. Data source are defined separately for each tinyPM project, so you will probably filter only issues from a particular project in JIRA too. To do that go to issue navigator and set filter for the issues that you want to have in tinyPM. Let’s say we want to import all open issues from project DEMO.

Saving JIRA filter

After filtering issues JIRA gives you the option to save the current filter. This is exactly what you want to do. After saving the filter under any selected name the important thing to get from JIRA is the requestId=10010 parameter which is your filter ID.

Defining tinyPM data source connected to JIRA

Now it’s time to create a data source in tinyPM. Go to projects and click on project data sources icon Project data sources. After that select “Connector for JIRA” and enter your JIRA URL, user name and password for the user that has access to JIRA and to created filter (unless you shared the filter with all JIRA users).

tinyPM sandbox with JIRA issues imported

That’s it! After few minutes you should see the currently open issues from JIRA imported into your sandbox. New onse will get there as soon as they are created in JIRA. You can create stories based on the imported issues or you can reject them them without flooding your backlog. They will get a proper comment in JIRA.

Connecting to POP3 mailbox

You can connect to any POP3 mailbox and tinyPM will import all e-mail messages sent to that address into the Sandbox. How can that be valuable? You can create a special sandbox like demo-stories@example.com where you can sent any of your ideas which you may later on upgrade to a user story in tinyPM. You clients can sent any project suggestion in a simple and convenient way directly from they favorite e-mail clients.

tinyPM data source connected to POP3 mailbox

To setup POP3 data source simply configure the mailbox just like you do that in your e-mail client software. After that tinyPM will pool that mailbox every few minutes looking for new e-mails.

You can limit the list of users that are allowed to send e-mails that will be imported by tinyPM using the allowedSenders property. This property accepts comma separated list of addresses and also accepts simple * wildcard in any part of the address. On the picture above we’ve limited allowed senders to the e-mail addresses in the domain example.com

That’s all you need to do to user the power of new tinyPM sandbox. But stay tuned as new cool connectors are coming soon! If you have any suggestions for the connectors that we should provide next please don’t hesitate to post them on http://feedback.tinypm.com