Permanent Web URLs for PBIs (permalinks)

Edit Subject

Indeed we face the same issue.

The Web Reports are quite static. With some very basic embedded javascript the resulting pages could have a TOC (Table of Contents), expand and collapse feature on modules, links from story keys to the web application ...

Currently everything you see is static and you have to go back to the product backlog and find stuff by searching. I would rather have a report with story titles and the link to the story description in the application itself.

---------------------------------------

Just that you understand how such a simple feature would help the very challenging product ownership we have over here, below the background on our process:

We have a highly customizable core product already in production since last year, for the investment fund industry, a relatively new business within a fast changing environment, therefore we continuously improvement this product along with bi-weekly sprints.

The scrum team responds to the front & maintenance teams (who run or support customer projects) with bi-weekly internal releases of the core product.

The product backlog is compose of prioritized project requirements (coming from different customer projects) which Product Owner and Team translate into reusable product features to burn-down.

Product Owner has then as main stakeholders, on one side project managers of running projects, on ongoing building / stabilization, and support manager of projects already in production.
Projects have external release plans. Product has a bi-weekly internal release plan.

Since project managers care only about their customization projects and ROI on project level, Product Owner has to balance all stakeholders’ wishes, sustain product together with the Team in the long run (by means of translations of customer specific requirements into configurable and reusable product features, and by means of proper architecture and design), and make sure that external releases are planned as a multiple of internal releases.

I would like to be able to create a URL which resolves to a particular user story. This would be useful to include in email, Wiki entries etc.

This reply was created from a merged topic originally titled
Web Report for individual user story.

Could this be something more than just a Web Report when you get to it? Could the PBI be editable (if you have the rights), for example? Could you navigate to the associated Tasks and update them?

Thanks

Mike Brown
ProQuest

The ability to link directly to an item and to a task would make it easier to integrate Scrumworks with our other tools. Right now it's hard to even send someone and email that will direct them to a task. We're having to duplicate data in Scrumworks and in Bugzilla just so we have something to link to.

After following the link it would be best to be able to view and update all aspects of the item or task.

Permalink to userstories/PBIs are a must have to be able to reference userstories/PBIs in wiki-pages, source control commit messages and so on.

Please implement this is your next release.

To underscore how important it is, we switched from Scrumworks to Mingle just for this feature. It's absolution essential for our work flow to be able to link to individual features, stories, tasks, etc.

Is it possible to have Links of Backlog Items in Basic Scrumworks? I would like to just send the URLs across, so tht person can directly go to the item in web/java interface.

This reply was created from a merged topic originally titled
Direct URLs of backlog items??.

I wanted to make a note in this topic. This feature is now available through our integration to TeamForge.

For details on the single platform solution see this page: http://www.collab.net/products/integr...

Just briefly; the integration between ScrumWorks Pro and TeamForge allows us 2 way synchronization for backlog items and tasks. When these items are TeamForge they enjoy the benefits of any other TeamForge artifact.

This has opened up a great deal of Application Lifecycle Management functionality for ScrumWorks Backlog Items and Tasks.

This isn't to say that the idea of direct URL links to PBIs isn't still on the ScrumWorks Backlog, every Idea on this community page is still a PBI or set of PBIs. However, I did want to make it clear that this feature is available *now* with the new integration.

If you are interested in the integration, or information on TeamForge, please feel free to contact us.

Another vote for permalinks to PBIs. (Even tasks) We have numerous wiki, issue tracking, and version management tools at my company (not to mention email!) that make this a really glaring deficiency in Scrumworks.

Hi Ert,

I just confirmed with the Product Owner that this is a feature that is currently being constructed for the next release of ScrumWorks.

This is solved in the new 5.0 release with the advent of permanent, predictable links for backlog items. From the docs:

To open the full page editor:

- Click on the item key link from the My Tasks, Sprints or Planning page.
- Click on the item key from the item editor in the desktop client.
- By going directly to the backlog item's URL: http://hostname:port/your-scrumworks-path/item/item-key

Note that this mechanism provides a convenient and predictable way to share a single backlog item's contents (via email, IM, etc.).

Note: Editing fields in the full page item editor requires the appropriate permissions. However, any user with product access rights can view backlog items in this fashion.

I'm really excited to see this when we upgrade.