Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-17519

Fields missing from the Next Gen issue views

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • next-gen
    • None

      Issue Summary

      Fields missing from the Next Gen issue views

      Steps to Reproduce

      • Open a Next-Gen issue either via the board view or the full page view.

      Expected Results

      • The configured fields should be displayed on the right hand column.

      Actual Results

      • The configured fields would load on the right hand column and when the page is fully loaded the fields will dissappear.

      Workaround

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

            [JSWCLOUD-17519] Fields missing from the Next Gen issue views

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: JSWCLOUD Bug Workflow [ 3194107 ] New: JAC Bug Workflow v3 [ 3474765 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 3086233 ] New: JSWCLOUD Bug Workflow [ 3194107 ]
            Shannon S made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 408817 ]
            Ramon M made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Ramon M added a comment -

            Thanks for the patience. A fix for this bug has now been deployed and the fields for the Next-Gen projects should now be available again. We will now proceed with the closure of this bug. If any problem persists, please do not hesitate to reach out via https://support.atlassian.com.

            Ramon M added a comment - Thanks for the patience. A fix for this bug has now been deployed and the fields for the Next-Gen projects should now be available again. We will now proceed with the closure of this bug. If any problem persists, please do not hesitate to reach out via https://support.atlassian.com .
            SET Analytics Bot made changes -
            Support reference count New: 1
            Bugfix Automation Bot made changes -
            Priority Original: Medium [ 3 ] New: High [ 2 ]

            Rach added a comment -

            Agree with Scott this is a major pain on my teams productivity - My project is rendered useless right now and I've moved to general verbal discussions in Slack about who should be doing what. I cannot assign any tasks to a user normally (nor can anyone on my team) and other form fields are just missing completely and inaccessible. 

            The work around I've managed to work out today, which is NOT a long term solution by any means;

            1. View the ticket in backlog view, move it to the board. 
            2. Arrange the board by assignee swimlanes (there must be at least 1 ticket to your assignee already on the board for this to work)
            3. Drag the ticket from the unassigned swimlane to the assignee's swimlane. 

            Otherwise... Create the ticket in a different project, assign it to a user then move it into the next gen project??!!?? 

            I'm not sure this level of basic project instability is worth it for the only major advantage of roadmap epic view right now    

            Rach added a comment - Agree with Scott this is a major pain on my teams productivity - My project is rendered useless right now and I've moved to general verbal discussions in Slack about who should be doing what. I cannot assign any tasks to a user normally (nor can anyone on my team) and other form fields are just missing completely and inaccessible.  The work around I've managed to work out today, which is NOT a long term solution by any means; View the ticket in backlog view, move it to the board.  Arrange the board by assignee swimlanes (there must be at least 1 ticket to your assignee already on the board for this to work) Drag the ticket from the unassigned swimlane to the assignee's swimlane.  Otherwise... Create the ticket in a different project, assign it to a user then move it into the next gen project??!!??  I'm not sure this level of basic project instability is worth it for the only major advantage of roadmap epic view right now     

            Scott added a comment -

            Not really a workaround, but kind of: You can access all fields in the jira iOS app just fine.

            I need a fix or workaround for desktop ASAP though as this renders a couple of our projects useless.

            Is it a config in my account that's caused it? I've uninstalled recent plugins I've added and that doesn't seem to have solved the problem.

            Scott added a comment - Not really a workaround, but kind of: You can access all fields in the jira iOS app just fine. I need a fix or workaround for desktop ASAP though as this renders a couple of our projects useless. Is it a config in my account that's caused it? I've uninstalled recent plugins I've added and that doesn't seem to have solved the problem.
            Bugfix Automation Bot made changes -
            Priority Original: Low [ 4 ] New: Medium [ 3 ]

              Unassigned Unassigned
              rmacalinao Ramon M
              Affected customers:
              4 This affects my team
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: