Skip to content

General

51 results found

  1. Simplify the setup process

    Setting up a shared repository and creating users is quite technical and time consuming. Build a UI to fast track you through this process.

    20 votes
    vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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
    vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Render MarkDown (with Tables extensions) in the descriptions of Gherkin feature files and scenarios

    It would be cool if SpecLog would render the description parts of a feature file and the scenarios by interpreting MarkDown, ideally including the Tables extension.

    11 votes
    vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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
    vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Add item to a workspace by editing the list of workspaces of the requirement

    The details of a requirement show the workspaces that this item currently belongs to. This list currently allows me to open the workspace, and remove the item from the workspace.

    I suggest you add the possibility to add the item to a workspace by making this list editable like the list of tags of a requirement. When I start typing, an intellisense list should appear with the workspaces that match my input.

    8 votes
    vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Display - last updated by [user]

    Display additionally to the date updated also the username that last updated the requirements/ACs.

    1 vote
    vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Provide more guidance about using SpecLog whilst working with Clients

    I would like to see more guidance on the different ways that SpecLog can be used whilst working with Clients on the Requirements for their Project Work and on helping them to visualise progress.

    Should I always generate Word documents to share with them. Is it appropriate to give them (temporarily?) a SpecLog Client and a cloned repository? Or something else?

    Thanks

    8 votes
    vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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 votes
    vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    With 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-ImportExport

    If 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.…

  9. Display SpecFlow execution results in SpecLog

    SpecLog allows to link SpecFlow Gherkin files to requirements. This way you can build up a living documentation map, that describes in detail the existing functionality of your product, guarded with automated tests.

    Test execution results, however, are currently not visible in SpecLog, but must be obtained from an external source (e.g. an HTML test report generated by the build server).

    To better allow seeing a "living" documentation map in SpecLog, we want to visualize test execution results of feature files that are linked to SpecLog requirements. This could be an overview "heat map" of test stability displayed on the…

    34 votes
    vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Publish integration API + open source existing integrations for work item tracking and source control

    SpecLog currently supports synchronizing requirements with work items (TFS2010) and linking Gherkin files to requirements from source control (TFS2010, GIT, fileshare).

    To allow users building and customizing their own integration to other source control and work item tracking systems, we want to publish and maintain the existing integration on GitHub.

    14 votes
    vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 0 votes
    vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 3 Next →
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base