General
346 results found
-
Allow attachments on comments.
We want to use the comments as ways to document conversation between marketing and engineering. Part of that might include spreadsheets or documents. Currently attachments can be added to a card, but not within the flow of the comments. And only by members which for us are marketing folks.
6 votes -
View multiple maps at once
Combine multiple roadmaps from different teams into one larger overview roadmap. Currently our teams have swimlanes on a physical board and we would like to move to a digital solution some day.
24 votes -
Integrate with Product Management tools
Have you guys looked into possible integrations with Product Management tools such as ProdPad or Aha!?
51 votes -
Configure font and color options
Ability to configure front-end styles:
- Edit card color options with hex codes
- Choose a different font (we export maps for clients, and it would be nice if they were more on-brand)
4 votes -
Implement GitLab issue integration
Implement GitLab issues integration
82 votes -
3 votes
-
Add Custom Jira Fields to Cards
As a Jira admin, I would like to add/sync a custom field that I have created in Jira with a card, in order to ensure that custom field is filled out upon card/user story creation.
Use Case:
As a Jira Admin, we require a value be selected for a custom field before creating a user story in Jira. When creating stories from StoriedOnBoard (SOB), the custom field is not available and will shoot back an error when attempting to push a card to Jira. This forces users to create cards in Jira and pull into SOB and devaluing the use…43 votes -
59 votes
-
3 votes
-
Option to hide "Done" tasks
You could hide "Done" tasks which would help to concentrate on the remaining tasks.
22 votes -
2 votes
-
Add auto ID cards
Add automatic ID card as a realized in JIRA. You can make an optional feature in the storymap settings.
15 votes -
Tag cards and search for tags
Tagging for cards, similar to Jira's implementation. These do not necessarily need to show up on the storyboard, just in the details.
7 votes -
Establish dependencies between cards (link related cards)
It would be useful to link dependent cards across or within activities and show/hide this dependency as a line arow between the cards
111 votes -
WHen cards a recreated, add an autonumber so the cards have a unique identifier for use in export to other systems.
Auto-numbering of cards for export reference
16 votes -
Add card priorities
Priorities (MoSCoW)
18 votes -
Maintain initiative/epic/story relationship when synching to/from JIRA
The import and export is flat and does not maintain the "Agile" issue hierarchy.
Blue cards should be initiatives, yellow cards should be epics, and white cards should be stories.
FYI the only way JIRA supports initiatives is using labels, which is actually pretty good.
In order to do this you may need the user to manually map each card tier to an associated issue type in their jira project.
If this was implemented, when importing a full project from JIRA you would effectively have an instant organised story map. The current format requires a lot of fixing up after…
21 votes -
Importing updates to a map from Excel
Import from Excel
You have the export mechanism working, it would be nice to be able to export, do massive update and import back.
Or, do initial import of cards in a single action from excel sheet.
21 votes -
Export comments on cards
It would be nice to add the comments on a Card in the export to office xml workbook with the format Backlog.
37 votes -
56 votes
- Don't see your idea?