General
51 results found
-
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 -
Show detailed error information on the UI.
When you get an error on the client, for instance connecting to a shared repository, it shows a generic cannot connect error.
Show the underlying reason in the UI so that you don't have to go through the process of enabling logging and hunting for the errors in the logs.
5 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 -
Indicate a criterion has an attachment when collapsed
Currently there is no telling if a criterion has an attachment unless it is expanded. It would be efficient to be able to spot attachments without having to expand all of them.
5 votes -
Use all the screen estate on a widescreen monitor
When I use speclog on a widescreen monitor it is not utilising all the space. In conjunction with another piece of feedback I gave on table formatting, this would greatly improve the usability of the tool.
4 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 -
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 -
Export/Import workspaces
While it is possible to work collaboratively on a Repository via a SpecLog server setup, it is not possible to work locally and then incorporate that into the server repository.
In my team there are three people that have been working on different aspects of a system and therefore have been working in different workspaces.
What we would like to do is create a repository and import our local workspaces.4 votesWith the new released SpecLog 1.3, you can merge stand-alone repositories, including workspaces, using the Excel export/import and later publish them as a shared repository on a server:
+) Excel export now can also export positions of cards: https://github.com/techtalk/SpecLog-Resources/wiki/Excel-ImportExport
+) Excel import now works for existing stand-alone repositories: https://github.com/techtalk/SpecLog-Resources/wiki/Excel-ImportExportIf you export your local workspace to Excel and import them individually into one repository, you should be able to merge.
You should just export/import the workspace you actually want to merge. If the workspace name already exists in the shared repository, SpecLog will create a new unique name. So you cannot import into an existing workspace parts of the map, but always just into a new workspace.
However, to merge maps into one workspace, you can copy/paste the imported workspace into the existing workspace after importing it.
The import does not merge requirements, but duplicates them when they exist already.…
-
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 -
Allow tagging of user story as story or task for TFS integration
When we refine user stories they end up being mapped to stories and tasks. We would like the flexibility to create refinements as stories sometimes.
4 votes -
Toggle Grid lines
Now that SpecLog snaps cards to a grid, it would be nice to be able to toggle the grid to display lines for easier alignment and organization of the cards.
3 votes -
Make title editable
I cannot figure out how to edit the title of a user story card (or any other card)
3 votes -
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 -
Provide translation
It would be nice if you could provide traslations for card templates and exported requirements (especially for HTML version)
3 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 -
Select a bunch of story cards. Speclog rearranges them neatly into a vertical stack (one under the other) sorted by backlog order or effort.
This will make it easy to create visual backlogs.
Simple case would be 1 wide x n deep. But 2 or 3 horizontal and n deep might be good if there are a lot of cards.The opposite feature might also be cool - select a bunch of cards and use their relative height to set the backlog order / priority. This way you could have conversations about the cards, moving them around on screen as you talk and then have Speclog 'save' the priority.
2 votes -
Allow tagging of criterion or parse out type of criterion
When adding criterion it would be more efficient to be able to tag them as Scenario:, Background:, Scenario Outline:, or when added manually the parser will parse the tag.
Currently if you manually add 'Scenario:' it will generate a scenario as "Scenario: Scenario: This is a scenario." Worse yet if a criterion is being used as background it will parse into "Scenario: Background: these are background steps."
2 votes -
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 -
Split screen/Multiple windows
Be able to view two separate tabs, either in split screen or in separate windows without having to open a separate instance of SpecLog.
2 votes -
1 vote
- Don't see your idea?