We need the ability to make standard and custom fields mandatory for existing records.
When a record is being edited, the UI should flag empty required fields so that the user is prompted to update them. This will help us ensure that critical inf...
Nathaniel Collum
almost 6 years ago
in Account settings
13
Future consideration
We have two portals, one for internal users and one for customers. The customer portal only needs a simple list of categories - no children categories. The customer portal is submit only.
For the staff portal, after a product manager has looked at...
Guest
over 9 years ago
in Ideas / Ideas portal
9
Future consideration
Enable the user to report on the values of a field based on its history. maybe a calculated field property where you indicate the field and the version back for that field. History(Custom_Field1,1) would show the value of that field one change bac...
Steve Podzamsky
over 4 years ago
in Reports
6
Future consideration
Similar to Capacity line in the feature board , we would like a target, commit, and stretch line with user defined % of capacity. Ex, 80% = commit, 100% = Target, 120% = Stretch with 3 lines. This way I could have a quick visual of my capacity in ...
Guest
almost 9 years ago
in Features
1
Future consideration
The record lists presented in My work almost display everything I need to know to prioritize my day and take action on the most important work. To really use these pages effectively, I need the ability to customize the data presented in the record...
Nathaniel Collum
almost 2 years ago
in My work
1
Future consideration
Expand/Collapse Release View to include Requirements
It's critical for our teams to see Features AND Requirements on the Release (Overview/Details View). You should be able to continue expanding down the hierarchy from Epic > Release > Feature > Requirement all within the Gantt.
Guest
over 6 years ago
in Releases
7
Future consideration
The new User Story Map functionality is really good and we've started using it for some cases. What would be really useful is to be able to configure the cards in the say way we can on the feature boards. This would allow a user to select the diff...
John Biltcliffe
over 5 years ago
in User story map
4
Future consideration
Copying an epic should also copy the associated features
Currently, if I want to copy a Master Feature, I must copy the Master Feature, then copy each associated Feature and map them to the Master Feature. This is time consuming and doesn't make a lot of sense.
doug evans
about 6 years ago
in Epics
9
Future consideration
We have a central point of contact for users to get in touch with us. It is via JIRA Service Desk. To keep it central, but efficient, it will be good if a submission into JIRA Service desk can take a particular issue type and automatically submit ...
Guest
over 8 years ago
in Ideas
15
Future consideration