General

  1. 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 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    we’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).

  2. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow creation of colour sets.

    This may seem trivial but we use a larger number of card types than there are colour sets available. With SpecLog being such a visual system, it would be nice to have the freedom to colour at will.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Visualize DONE progress in Story Map

    To be able to communicate progress and re-negotiate scope using story maps, it may help to convey DONE state of items visually. E.g. by placing a small green traffic light on the card. To avoid excessive tagging we recommend mapping to your ALM state 'Done' which would be quite generic if you provide a simple mapping table per item type. This feature might be coupled with sister request on reporting test stability, but not necessarily mixed into same indication.

    42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add a field Stack Rank to the user stories.

    The export to html enables to sort user stories by stack rank.
    Stack rank is synchronized to TFS.
    It will help a lot for planning, providing to customer the backlog in html ranked by stack rank.
    Optional: automatic sorting of user stories by stack rank: I select user stories, click X: all user stories piles up according to their stack rank.

    p.s.: I know that Speclog is not designed for planning but this stack rank is the only missing feature that enabling me to do all my work in Speclog.

    44 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

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

  • Don't see your idea?

General

Categories

Feedback and Knowledge Base