Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update backlog order based on votes doesn't actually change backlog order #24

Closed
hintbw opened this issue Nov 27, 2018 · 7 comments

Comments

Projects
None yet
5 participants
@hintbw
Copy link

commented Nov 27, 2018

We voted on our list of backlog items and then clicked on the update backlog order and it didn't actually update the backlog order of the items. They remained in their same order. This is obviously undesired and defeats the purpose of using the voting extension for us (in large part - we worked around by taking screenshots of the order, but there isn't even a way to export the list of items with the vote data so we could preserve the order in some way).

@MTRH

This comment has been minimized.

Copy link

commented Jan 7, 2019

I experience the exact same issue.

@bugerry87

This comment has been minimized.

Copy link
Contributor

commented Jan 17, 2019

image
Did you press this button?

@hintbw

This comment has been minimized.

Copy link
Author

commented Jan 17, 2019

Yes I did.

@bugerry87

This comment has been minimized.

Copy link
Contributor

commented Jan 21, 2019

We need more information about your environment, please.

Product: Azure DevOps Service / Azure DevOps Server (TFS)
(Version):
Process Pattern: Agile / Scrum / ICCM / Custom
Voting Level: Features / Requirements / Bugs / ...
Browser:
(OS):

AIT_VoteExt_EnvForm.txt

@hintbw

This comment has been minimized.

Copy link
Author

commented Jan 23, 2019

Azure DevOps service

Custom process based on scrum

Requirements (we have bugs as well as two custom work item types that also appear on the requirements backlog)

@BarbaraGoeller-AIT

This comment has been minimized.

Copy link
Collaborator

commented Feb 1, 2019

Hi Brett,

I think the 'Apply to backlog'-functionality does not work correctly in your scenario. since you do not have only requirements in your backlog but you do vote only on these. I'm sorry for any inconvenience.
We currently implement some major improvements including to make the 'Apply to backlog'-functionality only available in valid scenarios. This will be included in the next release.

Best regards
Barbara

@florianbader florianbader added the bug label Feb 16, 2019

@BarbaraGoeller-AIT

This comment has been minimized.

Copy link
Collaborator

commented May 9, 2019

Hi Brett. Today we released a new version of the extension which should solve the problem. Amongst other very cool new features, we introduced voting types: so from now on you can choose between backlog-based and (flat)query-based voting when creating a new one. For backlog-based votings you can apply the results after the voting is terminated and it should work correctly. We would like to get any feedback from you.

Best regards
Barbara

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.