Suggestions on setting up a wiki page that contains known issues pulled from version one directly
Robert Lazorchak
All,
We are trying to look into a way of doing the following thing:
Currently during testing and shortly after release, we encounter items that should be labeled as known issues so all of our customers can see the list.
We would like to add a custom field to our defects in version one that says something like “known issue” with a check box.
We would then like a way to have this information pulled from Version one and displayed on either a web page or a wiki page so that customers can simply check the page from time to time to get the latest known issues with that particular platform.
Does anyone have any good suggestions, ideas on the best way to do this.
Thanks,
Rob Lazorchak
Product QA
Metrico Wireless
The information contained in this e-mail is intended only for the individual or entity to whom it is addressed. Its contents (including any attachments) may contain confidential and/or privileged information. If you are not an intended recipient, you must not use, disclose, disseminate, copy or print its contents. If you receive this e-mail in error, please notify the sender by reply e-mail and delete the original message.
Robert Lazorchak
Sorry forgot to include 1 more thing, we would like the solution to pull and post the data either each day or weekly.
So we make sure our known issues list is the latest and greatest list and we aren’t having to manually update both version one and the new wiki page.
Thanks again for any help you may be able to provide.
Rob
--
You received this message because you are subscribed to the Google Groups "VersionOne-users" group.
To post to this group, send email to
versiono...@googlegroups.com.
To unsubscribe from this group, send email to
versionone-use...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/versionone-users?hl=en.
The information contained in this e-mail is intended only for the individual or entity to whom it is addressed. Its contents (including any attachments) may contain confidential and/or privileged information. If you are not an intended recipient, you must not use, disclose, disseminate, copy or print its contents. If you receive this e-mail in error, please notify the sender by reply e-mail and delete the original message.
John.Ai...@mitchell1.com
Rob,
We use the Issue artifact in VersionOne rather than a Defect for this. That way you can easily view the Issues for any release and see what is included.
Issues can also later be converted to either Stories or Defects when they do become actionable in a release or subsequent release. Unfortunately the reverse is not the case now with VersionOne; so if the artifact starts as a Defect it does have to be converted manually to an Issue. To work around this limitation, our Defects generally start as Issues and are converted during our assessment process if appropriate and actionable in the release.
Regards, John
Sr. Software Manager
Mitchell1
“The key to successful leadership is influence, not authority.” –Kenneth Blanchard
katia sullivan
Don't forget hat VersionOne has an open API. Please feel free to check into our documentation and the SDK to explore the possibility of making this happen.
Cheers,
~katia
Robert Lazorchak
I didn’t forget I was hoping someone had already done something like this already so we could just copy what they did. ;)
Will check out the documentation and see what we can do.
--
You received this message because you are subscribed to the Google Groups "VersionOne-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/versionone-users/-/-0sL_G19qzsJ.
To post to this group, send email to
versiono...@googlegroups.com.
To unsubscribe from this group, send email to
versionone-use...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/versionone-users?hl=en.