Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-76349

Story Points custom field can be edited/viewed even though the field is removed from the Edit/View screens

    • 8
    • 22
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Update - 13th of August  2024

      Hi everyone,

      Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.

      Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.

      We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback.

      Ahmud
      Product Manager-Issue View 
      aauleear@atlassian.com

      Issue Summary

      In the Jira new issue view, Story points custom field can be viewed and edited even though the field has been removed from the View and Edit screens associated with the issue type.

      Steps to Reproduce

      1. Create a Jira project with Scrum template
      2. Remove the Story Points custom field from the View and Edit screens
      3. Try to view and edit the Story Points custom field in the jira issue

      Expected Results

      The Story points field should no longer be visible/editable if the field has been removed from the View/Edit screens.

      Actual Results

      The Story Points field is still seen in the issue view and is editable even though the field has been removed from the View and Edit screens.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JRACLOUD-76349] Story Points custom field can be edited/viewed even though the field is removed from the Edit/View screens

            Hey, we noticed, that if we remove Story Points from edit and view - it's actually removed from issue. But if we put it only on view it's still Editable, that is not expected behavior.

            One more thing here: is that Story Points has additional UI on Boards

            and in Child Issues Area

            And it's still editable from Boards despite Story Points is not on any Screen. Though from the child issues area we're getting the error message that Story Points can't be edited because 'it's not on the appropriate screen'

             

            Our main Idea is to manage Story Point with Automation. And it's turned out that currently we can't.
            Atlassian please fix it.

            Slava Gefen added a comment - Hey, we noticed, that if we remove Story Points from edit and view - it's actually removed from issue. But if we put it only on view it's still Editable, that is not expected behavior. One more thing here: is that Story Points has additional UI on Boards and in Child Issues Area And it's still editable from Boards despite Story Points is not on any Screen. Though from the child issues area we're getting the error message that Story Points can't be edited because 'it's not on the appropriate screen'   Our main Idea is to manage Story Point with Automation. And it's turned out that currently we can't. Atlassian please fix it.

            Agree with the other comments, this is obviously a bug.

            Peter Daniledes added a comment - Agree with the other comments, this is obviously a bug.

            This should be a bug not a feature request.

            And we need this fixed!

            Eleni Wagner-Oikonomi added a comment - This should be a bug not a feature request. And we need this fixed!

            Please fix this

            Brent Powell added a comment - Please fix this

            How can this be low priority? "We just want to ignore it" doesn't mean this has low priority. Users cannot make this field read-only which is a serious lack of functionality.

            Andriy Kozynets [PROFISEA] added a comment - How can this be low priority? "We just want to ignore it" doesn't mean this has low priority. Users cannot make this field read-only which is a serious lack of functionality.

            Jeffrey Bistrong added a comment - - edited

            this is a feature gap from the old view, please address this gap ASAP. It works fine in the old view!!!

            Jeffrey Bistrong added a comment - - edited this is a feature gap from the old view, please address this gap ASAP. It works fine in the old view!!!

            Ankit Garg added a comment -

            How this can be a low priority? This is a serious bug with the basic functionality of Jira and a must have for most of the teams.

            Ankit Garg added a comment - How this can be a low priority? This is a serious bug with the basic functionality of Jira and a must have for most of the teams.

              Unassigned Unassigned
              b678926ca497 Bopanna
              Votes:
              41 Vote for this issue
              Watchers:
              44 Start watching this issue

                Created:
                Updated:
                Resolved: