General
346 results found
-
Support Jira issueLinkType integration with Card Annotations
It would be good to expand the integration options with Jira, by adding an additional import setting for 'issueLinkType' matching from Jira. Like with Jira issues you can match the states, I want to be able to say that if a Story has a linked issue with the type of 'is blocked by' then I can choose the relevant storiesonboard Card Annotation to display e.g. 'Blocked' or 'Depends on Other' This would then show in the card and support filtering of the board.
35 votes -
Export annotations in Excel file
Be able to export annotations linked to cards in the excel export
11 votes -
Filter import of GitHub issues by label
When enabling import of issues from GitHub to StoriesOnBoard, it would be very useful to filter/limit issues to import by GitHub labels.
For example, only GitHub Issues labelled as Epic/Story are imported into StoriesOnBoard.
1 vote -
Customize color for card and annotations
The list of colors is fixed, and I would like to have the possibility to choose myself which color to use for my cards and annotations.
For example, I could use a gradient color map about the value of my card.
2 votes -
Add the ability to export Board Discussions
The ability to export board discussions would significantly help in gathering artifacts, evidence and preparing for IT control meetings to show communication, approvals..etc from the project participants regarding the project.
3 votes -
Add productboard to the roadmap
Please consider ability to generate productboard features and sub features from storiesonboard and sync statuses and changes
3 votes -
Collections - Enable for WorkspaceMembers to organize by collections
As a WorkspaceMember of a consulting organization, I want to be able to organize our workspace by clients (collections feature would work) so that our numerous board are easy to find and track as we do additional work for the client and so I can get our 27+ PO organization to use StoriesOnBoard. However, I want our enterprise IT to continue to managing adding users (i.e. licenses) because this is our current process.
6 votes -
Save and name filters
- Need a way to save and name a filter. There are many Use Cases. For example, I'd like to set up Customer Journey's using filters. To make this possible I need to save the filter to come back to the same Journey.
- Need ability to save the filtered map. In other words need the ability to save a map once it has been filtered so that the newly saved map only has the result of the filter. So for example if I'm filtering to arrive at a Customer Journey, I can save the filtered map as Pharmacy sales rep. journey.
5 votes -
Allow Viewers to Participate in Brainstorming
It would be nice when in the 2-Layer view for Brainstorming if the Viewers (or viewers with permission) could at a minimum create new Cards/edit titles. This way brainstorming can include additional people beyond the PO responsible for creating/maintaining the board.
1 vote -
Include story card URL/link in backlog xls export
When using the export to xls function, we often want to pop back and forth from the story in the xls and the SOB story, so having the card URL in the row for that card would improve our productivity
11 votes -
Add the ability to bulk export stories or story collections
When creating a storyboard Collection, it would be extremely helpful to be able to export the entire Collection at once, instead of having to open the Collection, and open/export each individual storyboard one at a time.
4 votes -
Sync card annotations to external systems
Card Annotations should sync with Github tags, Jira labels, etc.
12 votes -
Bigger persona pictures / icon
Persona pictures are rather small and hard to see.
I generally use very descriptive images / icons for personas, would be great if they were bigger!
3 votes -
Have more than one box inside the user story card to separate parts of the story i.e. one for the user story, one for acceptance criteria et
Have more that one box inside the user story card to separate parts of the story i.e. one for the user story, one for acceptance criteria etc.
I would like to be able to separate each of these important pieces of the story. We also use exports, and some of the info is not included when exporting (comments example0
4 votes -
10 votes
-
Use components instead of Epics for the backbone
Components make more sense in the JIRA as the backbone (Second level cards) than Epics, as Epics should have a limited life compared to Components which is a way of grouping stories on how the user flows through the system.
4 votes -
19 votes
-
1 vote
-
Support Area paths in Azure Devops / TFS
Supporting Area paths in the DevOps integration would allow anyone to keep story work items in the proper team and or product.
Currently you can filter what syncs using a query, but new items go to the default area path.
If new work items could go to an area path (specified in the story settings) it would keep them in the correct Team/Product.
28 votes -
assign card colors automatically to Jira states
it would be very nice if the color of the cards is automatically mapped to the state of the card in jira.
for example:
* story is in a sprint
* the story is done
* story is on going
* ...9 votes
- Don't see your idea?