General
51 results found
-
Change the estimation field to allowing t-shirt sizes
A lot of customers I consult with are not using numbers for their estimates. They may be using S, M, L and XL etc.
Demanding a number is limiting them a bit.
10 voteswe’ll try to get this into the upcoming release. we need to check yet, whether/how this fits with TFS integration, as we sync the estimate to TFS workitems (if a TFS project is connected).
-
Have capability to deselect all requirements cards
There appears to be no way to (unless there is) deselect all the requirements on the screen. If there is no filter active, there appears to be occasions where one or more requirements are still selected. There doesn't appear to be a simple option (right click -> clear selection? or left clicking in empty space in the workspace) to deselect these items.
So that I don't accidentally move requirements around the workspace unnecessarily.1 vote -
Allow tags filter search to search case insensitive
As a user it would be useful to make the tags filter work case insensitive as this is a common pattern people are used to (especially for a tag which I can't actually determine when you may want a case sensitive tag search)
So that I can find tagged items without error.
1 vote -
Trigger client plugins (HTML-, Excel-, Word-Export) via a CLI
As a Speclog User
I want to export my requirements to HTML, Excel or Word with a command line call
so that I can automate the export and schedule it periodically to distribute the requirements as living document.3 votes -
Allow copying a single acceptance criterion as Gherkin
It's a minor Quality of Life issue, but when I add a new Criterion to a Requirement because of a new Scenario discovered after the initial discussion around a Feature, it would be nice to have a "copy" option to get the Header and Text at the same time when I go to add the Criterion to my .feature file.
1 vote -
make workspaces more informative by showing "calls" between stories as lines.
Structural relationships between stories are at least as important as hierarchical ones. It would transform the value of workspaces if you could see how stories call each other.
2 votes -
Add templates for User Story acceptance criteria
As a Business Analyst
I would like to have a template for User Story creation,
so that i have pre-filled structure of data which i need to fill in.18 votes -
Allow user definition of snap grid size
While the snap to grid is beneficial, the grid size is too fine to allow a clean organization of cards. Allowing the user to define the grid size would greatly improve the appearance of story maps.
4 votes -
1 vote
-
provide a richer text editor for the Criterions
we are now using SpecLog for all of our documentation and miss the ability to format such things as:
- tables
- indenting of lists with mixed bullets and numbering
etc11 votes -
Allow TFS Work Item types to be mapped to different SpecLog entities
WE would like to be able to keep all of the SpecLog entities in TFS, but keeping them all as User Stories really doesn't work.
It would be great, for example, to make TFS Features map to SpecLog Business Goals.
23 votes -
Adding 3rd dimension to Storymap by allowing collapse/expand slices of User Stories
Jeff Patton suggested to collect these User Story cards on top of each other. Adding this feature could drive the users to use Story Mapping as it is intended to: differentiate visually the alternative stories and the slices of a User Story. Collapse/expand could be implemented similar to the way how it works in MindMap.
4 votes -
Edit the Title of a requirement from the Workspace when the cards display only the Title and not the details
When the workspace is zoomed to a level that displays just the title on the cards it would be handy to still have the possibility to edit the card's title.
Suggestion: by pressing F2 (convention from Excel) a text box for editing the title would be displayed over the card (inspired by Trello).
2 votes -
Add named swimlanes or containers to workspaces
Adding swimlanes or other visual containers with visible name would allow to better organize the Requirements in a Workspace by logical areas.
These visual aids would help when creating Story Maps in SpecLog.
5 votes -
Add filtering mechanism based on area path (at least) to TFS backward synchronization
Many projects (project teams) share the same TFS-project entity, structured using area path. When only some of the teams use SpecLog, they would receive all TFS WI-s created in TFS by all teams, as there is no filtering possibility.
1 vote -
allow TFS Product Backlog Items to synchronise with multiple SpecLog repositories
Add functionality to SpecLog that would allow multiple repositories to link with one project in TFS.
Currently, TFS Product Backlog Items can be linked to one User Story in SpecLog.
4 votes -
Straight line connectors
Teams using SpecLog felt that the line connectors are very confusing and messy. One person described a workplace of connected nodes as looking like a giant octopus. There are several UML diagram tools out there like Visio that organize line connectors using some sort of algorithm that cleanly abbreviates intersections, and toggle lines to straight or curve types. Honestly, if the line connectors are straight lines it would look much better.
5 votes -
allow the repository file name to either remember the last selected location or be set in the client config file
As discussed over twitter we have slightly locked down PC's and by default when connecting to a shared repository the SpecLog client defaults to the Documents folder. For is this is a UNC path and for some reason this causes the application to exception. If I map a drive to the same location and use the mapping this works. However next time you connect you have to set this again.
Great product by the way.
1 vote -
Web Version
It would be nice to have a web version of SpecLog. In the era of Html5 and the explosion of web app, it's such a pity to stick to windows desktop version. I find it as old school to go and download a client, take care of updates be sure that .net version 4 it's installed on your machine.
23 votes -
Define parents and refinement in the same way as defining tags on a particular requirement
I really like the way how simple it is to add tags and I was wondering if there is a quicker way to define refinements and parents than using drag and drop.
e.g. within a text box i can start typing and the system will provide an instant list of matching user stories (just as an example) similar to the requirements search on the workspace across workspaces. When selecting a suitable user story the system is coping it automatically to the current workspace with the appropriate linkage.
Regards
Johannes1 vote
- Don't see your idea?