General
346 results found
-
Trello lists as statuses
Trello config: optionally replace storiesonboard statuses with Trello board list name (you already know those from being able to map them against your own statuses). Offer to map against custom color instead of storiesonboard statuses.
4 votes -
bitbucket's jira integration
bitbucket integration
there's jira inside bitbucket so it perhaps could work without too much extra effort
4 votes -
paypal using to pay
possibility to pay using paypal
4 votes -
Link multiple cards to the same JIRA issue.
"There are sometimes repeated tasks under different activities on the board. Also sometimes multiple tasks translate to one story in JIRA. In any case, one should be able to link multiple cards to the same JIRA issue to keep the status consistent."
4 votes -
4 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 -
Cards should show estimation number
Cards should show level of effort estimation in dashboard view.
4 votes -
4 votes
-
4 votes
-
4 votes
-
WYSIWYG Editor
Why do we have to remember markup options when every descriptor form box currently on the web integrates a WYSIWYG editor (like TinyMCE) into the field, so it is much easier to format and style the copy you are entering.
4 votes -
Story map visibility settings on a workspace level
It would be nice to have an option to disable the visibility of all story maps e.g "Workspace visible" for the entire Workspace, so users can't set this option by mistake.
4 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 -
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 -
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 -
Bulk edit story descriptions
We are on an iteration planning session. We'd like to go through all the stories selected for the iteration and discuss their purpose, acceptance criteria, specification. We'd like to use the story map to guide through the process showing us each stories' details at once (without opening and closing each of them), much like as if we were reading a document.
3 votes -
Restrict size estimate to one of a set of allowed sizes
For example, in our Scrum shop, we only use 1, 2, 3, 5, 8, 13, 20, 40, 100, ?
3 votes -
Synchronize effort Field between stories on board and tracking system
Link card effort measure to matched field in external tracking system i.e. Two-way sinking between effort fields.
3 votes -
Provide goals for one or more rows
Provide a way to specify the goal of a lane. E.g. place the goal on the first column so that one or more rows can be grouped to a specific business goal.
3 votes -
Synchronize points given to a card with Pivotal
Synchronize points from Pivotal, as long as they match in value
3 votes
- Don't see your idea?