Stephen McCafferty
My feedback
8 results found
-
23 votes
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment Stephen McCafferty
commented
You can draw a selection box if you hold down Shift or Ctrl while dragging. Requirements are only added to the selection if the entire card is within the selection box.
You can use the same shortcut to clear a selection: just drag a very small selection box and the current selection will be removed. I appreciate this is not really intuitive, but as you say, there would be a conflict with the drag-to-scroll command if a click cleared the selection.
I have updated the hotkeys section in the documentation with this information.
-
44 votes
we’ll look into this.
An error occurred while saving the comment Stephen McCafferty
commented
How do you imagine the stack rank being used on the workspace?
The optional automatic sorting of user stories sounds interesting, but I'm not sure I fully understand the scenario:
a) Stack rank -> workspace position:
A group of user stories is selected, that will be rearranged according to tack rank.
+) How should the stories be positioned according to stack rank?
+) If we rank by y-axis (highest prio top, lowest bottom), where should the card with the highest position be placed (under which the lower ranked cards will be placed then)?b) workspace position -> stack rank
The reverse operation would also be interesting, I think:
A group of user stories is selected, and according to their position on the workspace, their stack rank is updated. However, in this case, we should also be able to deal with slices in story maps - so stories on the same y-axis level should be ranked before stories below.
Some questions for this scenario:
+) What should be the initial stack rack, under which all the other stories are assigned? We could use the current stack rank of the top left story on the workspace, and rank all other stories after.
+) How should we rank stories on the same x-level? We could go from left-right, but maybe somebody has a better idea?c) Working with slices
In story maps, there is the notion of slices. These are currently supported through tags in SpecLog (cards with the same tag belong to a slice). Slices are also used for planning and prioritization.
+) How should a slice of stories be stack ranked?
+) How should slices be stack ranked after each other? -
3 votes
An error occurred while saving the comment Stephen McCafferty
commented
The card title is just one of the four possible fields (Actor, Goal, Value, Title) a requirement can have. There is a HeaderField property in the <CardTemplate/> element that defines which of these should be displayed as the title of the card.
More info can be found here: https://github.com/techtalk/SpecLog-Resources/wiki/Customize-Card-Templates
Or did I misunderstand your suggestion/question?
-
20 votes
An error occurred while saving the comment Stephen McCafferty
commented
Setup of shared repository: Do you mean setting up the server initially, or publishing/creating a shared repository on an existing server?
Creating users: I guess you mean initial creation of users on the server, not the individual user permission assignments (that are available under "manage repository"). Correct? Of course, when we provide a better UI for creating users on a server it would also make sense to also set their initial repository permissions when creating them.
I can imagine a publish repository and create/assign users wizard, where you can create/assign users in the same step with publishing a repository. Created users would need to receive their access token (in Email), all users would receive a notification/instructions how to connect to the shared repository. Is that what you'd be looking for?
-
8 votes
might be coming in Release 1.8
An error occurred while saving the comment Stephen McCafferty
commented
See also the question to the other idea you posted (https://speclog.uservoice.com/admin/forums/154795-general/suggestions/3309557-move-copy-item-to-another-workspace): at which position should the cards be added?
-
34 votesStephen McCafferty
shared this idea
·
-
14 votesStephen McCafferty
shared this idea
·
The new V3 plugin for TFS in SpecLog includes the option to choose what type of TFS item to synchronise a card with.
There are some caveats: if you are synchronising in both directions, then the mappings need to be unique in both directions to be resolved. For example, you can only map one type of SpecLog requirement to Product Backlog Items in TFS if you are synchronising from TFS to SpecLog as well. If multiple types of SpecLog requirements are mapped to PBIs, there is no way of back synchronising the PBIs, as the target SpecLog requirement type cannot be uniquely identified.
If you have previously been using V2 of the plugin, you should take care to follow the migration steps in the documentation before enabling V3. V3 uses a database table for synchronisation and this table is initialised with your current state when first migrating. This is important to ensure that previously synchronised requirements continue to be synchronised correctly.
More information on the V3 TFS plugin can be found here: https://github.com/techtalk/SpecLog-Resources/wiki/SpecLog.TFSPlugin.V3