The export approach involves downloading Avery's print wizard and setting up a template. Then each time you want to print your stories, go to the view in V1 that has the stories and columns you want to see on cards. You'll then do a few steps to export the stories into a spreadsheet and use the Avery tool to format the stories (into another document) and then print them on special Avery stock. The advantage to this approach is being able to select which values you want on the card and where you want them. That's all I'm going to say about this approach.
The Browser Approach
To keep this from getting too complex, I'm going to describe what you need to do if VersionOne is hosting your instance. If you are hosting it yourself you should be able to figure out what to do by reading the original post.
Generally, we are going to get all the stories formatted as cards on a web page, then we're going to print from the browser onto cards. To see all of the stories in the system, use this URL:
For this and all the URLs below, you will need to replace "servername/v1instance" with your actual server and instance name. (Hint: look a the URL you use to access V1.)
Of course, you most likely will rarely want to print every story card. Thankfully, you can add some filtering. I'll provide some examples. You may have to do a little guessing, experimenting and URL manipulation, but I'll tell you how to approach that.
You can control which stories are returned by adding some query strings to your URL. For example, to see the stories for "Sprint #1", use the URL
Note the %23 in place of the hash symbol. You'll need to handle special characters in your URL appropriately.
To see the stories for "Iteration 7":
To see the stories for "Sprint #2" that are OPEN (64):
To see the stories for Iteration 6 that are OPEN (64):
To see the stories for Iteration 6 that are CLOSED (128):
You may want to do more filtering than in the examples here. To see what all the attributes and values are, leave the xslt out of the URL as follows:
There might be something useful to you in the Meta:
And you may need to refer to the Meta API and the ReST API documentation for V1's sdk as well as the article Getting Started with the API.
Now for Printing
Now that you have the stories you want to print formatted as story cards in your web browser, it's time to print them. This xslt we are using is set up to print two stories per page on letter size paper. If this is acceptable to you, you'll likely need to scale the print job to 80% or 90% when you print. Alternatively, you could go the extra mile and set up your browser to have no margins and no header or footer. But if you do that, you'll likely want to reset all of that once you are done printing.
That is certainly the easiest approach if you have a paper cutter handy, but with a little more effort we can print those directly onto stock index cards. To print those on a 3x5 card, set your browser as follows:
- page setup: landscape, no margins, no header or footer
- print, properties, paper: 3x5
- print, properties, effects: leave set to actual size
- print preview: scale 50%
Question of the Day
Have you found any other approaches to print story cards from VersionOne?