JIRA and Trello integration
Here's how we planned to work with JIRA and Trello:
The team/product owner/customer is planning in StoriesOnBoard. They are brainstorming, coming up with ideas, putting them onto the board
/a. in the unscheduled task if it's just a fuzzy idea
/b. or in a distant release if they think it's needed but not so important at the moment
/c. or in the next release if it's a must
They take notes of their ideas in the descriptions to help them remember later what they thought about.On a sprint/release planning session the team selects and discusses the most important stories and moves them into the next release. For the selected stories they (or the customer or a business analyst) identify acceptance criteria, write high level specification (only with the details that's needed to understand the requirements).
When the team begins their work on the release, the Product Owner sends the stories into JIRA/Trello (all of them, or just the specified ones). Issues/Cards automatically created in JIRA /Trello with the title and the description taken from StoriesOnBoard.
The team is working on the release: discussing the specifications, modify/complete them if needed in JIRA/Trello, update the issue's statuses in JIRA/Trello and they automatically get refreshed in StoriesOnBoard too.
While they are working on the release they can always have an overview of how the release is progressing in StoriesOnBoard. They can select new stories into the current release or defer some to latter releases. If they have new ideas then they can put those also onto the board to the appropriate release. These are not reflected in JIRA or Trello till the Product owner is not sending them.
When they are finished with the release (all the tasks set to done in JIRA/Trello), they archive the release in StoriesOnBoard, so it disappears from the board with all it's stories.
Repeat with step 2.
What do you think? We’d love to hear your thoughts about how would it fit into your workflow.
AdminArpad Tamas
(co-founder, StoriesOnBoard)
shared this idea
It’s released!
-
Thanks for creating a separated idea for that Jay!
http://storiesonboard.uservoice.com/forums/276721-general/suggestions/7563318-sync-card-estimation-with-jira-estimation -
Jay Shah
commented
Can we see the Actual/Remaining Estimation of JIRA in SoB cards ?
-
It's released! :)
Thanks for your patience and your support! -
Maulik Modi
commented
Can we see Stories on Board to JIRA Integration?
-
Thanks for all of you for the great support! Sorry for the late answers. To tell you the truth we didn't want to promise another timeframe, because we already breaked the previous. But I can assure you that we are working on it. We had to rework the authentication scheme for allowing passwordless authentication with JIRA and it was unexpectedly complex. Now it's working for the main scenarios and most of the edge scenarios we could think of, but we are still testing and fixing these (what happens when the connected user's privileges are changing in the integrated systems, users deleted, projects go out of sync and the like).
-
@Dirk, please contact us in email at feedback@storiesonboard.com if you'd like to try it out before it's released. We would appreciate any feedback and help in testing.
-
@Stacy Thanks for your kind feedback!
May I ask you if you use any issue tracking tool? (like JIRA for example)
If so, how do you use it with your story maps (StoriesOnBoard)? What kind of details do you put onto the board and into JIRA?
Please let me share a few words about the background of StoriesOnBoard, why we started to build it.
In our vision StoriesOnBoard is an aid for planning products in a way that allows identifying the most important outcomes so that products can be built with less effort, less features yet more serving their purposes. We'd like to facilitate brainstorming on questions like "what would help the product's user the most in achieving her goal?" and "how can the product help reaching that goal with a smart solution and the least effort?"
That's why we'd like to keep statuses (and the process) simple and easy in StoriesOnBoard, and that's why we are integrating with tools like JIRA. Statuses in StoriesOnBoard are aggregated statuses for getting a high level overview, while statuses in an issue/task tracking tool are more deeper and customisable for the detailed implementation process and even can be different in individual projects.
What do you think? How does that sound? -
@Shawn In the first solution for integration there will be one to one connection only between the white cards and JIRA issues. No hierarchy or any other relation will be synced and handled between the two systems at first as these relations can be used in many different ways in JIRA.
> Does the card have a link to the JIRA ticket?
Yes they will be connected for a two-way sync. Modifying the JIRA ticket's status, title and description will update them in StoriesOnBoard (can be turned off) and modifying the white cards title and description will be propagated to JIRA. -
Brian Fitzpatrick
commented
Just checking in as well. I don't need a timeframe, just to know whether it's being worked on. My concern (and maybe others on the thread) is that is has gone silent since the last announcement in January that this would get released in February.
-
Dirk Diddens
commented
I love storiesonboard! Especially for high level release planning, this is (almost) exactly the tool I was looking for. Since our develpment team is relying on JIRA... we're very eager to test the announced JIRA integration. Could you inform us on status & forecast of this integration? Many thanks & keep up the good work!
-
Anonymous
commented
Status on Trello integration. Trying to adopt this across the company, but this is a must.
-
Stacy
commented
Love the tool so far!!! Everyone in our organization is excited to begin fully using the tool. One question I have is if it will eventually be possible to customize the card status options. It would be useful to be able to track what is "UX In Progress", what is "Dev In Progress", what is "In Test", and what is "Shippable", to track progress throughout a release.
-
Brian Fitzpatrick
commented
The Trello integration is what us to buy in to trying storiesonboard. Love the interface thus far and I think the most useful thing for us would be to have the acceptance criteria separate from the description so that it can be pushed as a checklist over to Trello.
-
Phil Borgnes
commented
Hi. Just checking in to see how your release with JIRA support is coming along. I have an eager team ready to rock!
-
Shawn McKenney
commented
Hi. We are looking forward to JIRA integration. The way we currently have things set up, the top blue card is being mapped to a JIRA component. The next level (yellow card) is being mapped to an Epic, and the white cards are being mapped to stories. I'm not really that concerned about the component level. Will the interface handle dependencies between tickets?
So, when step 3 is complete, do any dependencies (references) get created in JIRA? Does the card have a link to the JIRA ticket?
We are just starting to use the board, so we would like to use the system as you are designing it. Any tips/advice would be appreciated. I can give a more detailed explanation with screenshots if required.
Thanks!
-
@Anonymous
Thanks for the suggestion! Please vote for it here: http://storiesonboard.uservoice.com/forums/276721-general/suggestions/6954116-rally-integration -
@Phil
You'll be able to pull your existing issues from JIRA then map it out in StoriesOnBoard. Then the cards<->issues will be connected, so status changes in JIRA will be reflected automatically on your story map. Also the title and description fields can be automatically synced too (but that's optional).
-
Anonymous
commented
Great idea. If I may, would also love Rally integration. Our teams use both Jira and Rally.
-
Phil Borgnes
commented
Great to hear that there will soon be integration with JIRA. From the above description it sounds like the workflow is SoB => JIRA. What about the other way? How to start from our existing backlog in JIRA, map it out, and then bring it back into JIRA. Some diagrams on round tripping would help understand. Thanks.