Log inSkip to main contentSkip to sidebar
Something went wrong, please try again.
Create and track feature requests for Atlassian products.
  • More
    DashboardsProjectsIssues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

Open issues

  • All issues
  • Open issues
  • Done issues
  • Viewed recently
  • Created recently
  • Resolved recently
  • Updated recently
View all issues and filters
Order by Priority
  1. Suggestion
    JRASERVER-66870Allow custom fields of type "Text Field" to be used as the Statistic Type for the "Pie Chart" and the "Two dimensional filter" gadgets
  2. Suggestion
    JRASERVER-69110Option to add custom headers to be sent in Jira webhook
  3. Suggestion
    JRASERVER-70324Collaborative editing
  4. Suggestion
    JRASERVER-23013Allow multi-select and multi-checkboxes custom field types to use auto-complete renderer
  5. Suggestion
    JRASERVER-61788Change the handling behavior of emails containing 4 byte characters to avoid random increments of issue numbers
  6. Suggestion
    JRASERVER-73330Ability to use Watcher field through Basic Search
  7. Suggestion
    JRASERVER-32276When importing XML backups they should be converted into UTF-8 and have any invalid characters stripped
  8. Suggestion
    JRASERVER-37277Retrieve User Count via rest api
  9. Suggestion
    JRASERVER-70431Option to disable the user picker icon for the "Multi user picker" custom field in Jira
  10. Suggestion
    JRASERVER-78114Add full support for Amazon S3 and Amazon S3 compliant storages
  11. Suggestion
    JRASERVER-78193Document update request - Configuring an SMTP mail server
  12. Suggestion
    JRASERVER-78550Add support to COS on other than AWS cloud providers
  13. Suggestion
    JRASERVER-78733Update Webhooks API documentation for Jira 10
  14. Suggestion
    JRASERVER-78837As an admin, I would like the permission helper tool consider admin privileges when checking permission for projects.
  15. Suggestion
    JRASERVER-4233It would be nice to be able to save issues as "draft"
  16. Suggestion
    JRASERVER-8047 Bulk delete users
  17. Suggestion
    JRASERVER-40918Ability to view PDF, Word, and Excel Attachments Inline
  18. Suggestion
    JRASERVER-70380Enable Due Date field in Issue Collector
  19. Suggestion
    JRASERVER-71915Provide more meaningful message to SAML responses
  20. Suggestion
    JRASERVER-78839Mechanism for encrypting of custom properties for Jira, similar to secrets.secured-properties in Bitbucket 9.0
  21. Suggestion
    JRASERVER-70538Select query optimisation to improve performance for issues with large number of comments
  22. Suggestion
    JRASERVER-70455Quick search to include issue key
  23. Suggestion
    JRASERVER-66782Limit the Link type options available
  24. Suggestion
    JRASERVER-70638Archiving sub-task issue type
  25. Suggestion
    JRASERVER-70691Jira Data Center deployment with Hazelcast ECACHE
  26. Suggestion
    JRASERVER-72112Provide the ability to reuse a project key once its original value is altered
  27. Suggestion
    JRASERVER-5884Linking Version over projects
  28. Suggestion
    JRASERVER-36960Configure Tomcat so that it has a unique SESSION_COOKIE_NAME to prevent session overwriting for JIRA
  29. Suggestion
    JRASERVER-66300Improve Versions page loading in JIRA
  30. Suggestion
    JRASERVER-67849Replace Guava cache for frequently accessed caches due to concurrency and memory inefficiency
  31. Suggestion
    JRASERVER-69843Allow admins to grant user access to the External System Import functionality
  32. Suggestion
    JRASERVER-72122Insight Confluence Macro: Connected tickets as column/attribute
  33. Suggestion
    JRASERVER-15260Add ability to subscribe dashboards
  34. Suggestion
    JRASERVER-25308CreateIssueDetails URL does not fill in default value for Reporter field when user has Modify Reporter permissions
  35. Suggestion
    JRASERVER-75754Sprint Burndown for more than one Sprint
  36. Suggestion
    JRASERVER-43992Export system information on JIRA
  37. Suggestion
    JRASERVER-61221ordering of statuses (wf statuses)
  38. Suggestion
    JRASERVER-61378REST API parses date/time strings poorly
  39. Suggestion
    JRASERVER-65962Option to disable "Any logged in user" permission
  40. Suggestion
    JRASERVER-35422Create an option to make Work Description a required field
  41. Suggestion
    JRASERVER-62080Ability to Restrict Profile Editing
  42. Suggestion
    JRASERVER-68505Provide granular permissions for managing releases and versions
  43. Suggestion
    JRASERVER-74183Support for Amazon EFS lifecycle management
  44. Suggestion
    JRASERVER-78369Allow Jira administrators to disable the Update Parent Issue pop up screen
  45. Suggestion
    JRASERVER-6146Implement issue locking
  46. Suggestion
    JRASERVER-11297Multiple Attachment Delete
  47. Suggestion
    JRASERVER-71767Allow the creation of Sub-tasks when "jira.issue.editable = false" is set on the parent
  48. Suggestion
    JRASERVER-72553As a Jira admin, we'd like to have the Delete old attachment function in Jira UI
  49. Suggestion
    JRASERVER-78605Remove the "Confirm" button for Date Started to log work
  50. Suggestion
    JRASERVER-21888remove requirement for entering an email prefix in the SMTP Server config
Refresh results
<< Previous 9 10 11 12 13Next >>
549 of 7862
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-78605

Remove the "Confirm" button for Date Started to log work

Log In
Gathering Interest
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Issue - Time Tracking & Worklog
    • None
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Description:

      Within the "Log Work" section, it is a bad UI choice to have the user need to hit "Confirm" when they've already selected the date in the "Date Started" section.

       

      Reasoning:

      • When a user has already selected a date, an added redundancy of hitting confirm slows down the user. More often than not, its often overlooked, causing the work to be logged to the present day, instead of the intended day.
      • The "Log Work" is a high volume feature. Any UI changes need to be carefully implemented.
      • If there are errors with Date entry, the users can easily select "Work Log" and make the necessary changes there.

       

            • All
            • Comments
            • Work Log
            • History
            • Activity

            Poul Nielsen added a comment - 23/May/2025 1:13 PM

            Confirm button should be mandatory or removed

            Poul Nielsen added a comment - 23/May/2025 1:13 PM Confirm button should be mandatory or removed

              Unassigned Unassigned
              f865808f90df Ansh Mathur
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                17/Feb/2025 4:23 PM
                Updated:
                25/May/2025 2:25 AM
                • Atlassian Jira Project Management Software
                • About Jira
                • Report a problem
                • Privacy policy
                • Notice at Collection

                Atlassian