We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
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.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-13522

Need to improve the way the calendar-<locale>.js files are served

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 3.12
    • None
    • None
    • 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.

      After the JS and CSS improvements in JIRA 3.11 the calendar language translation file (e.g. the calendar-de.js file) is included from the calendar-language.jsp file.

      The problem is that if the user changes their language preference, until the cache expires, the wrong transaltion file will be served.

      Need to add all language files to the system-webresources-plugin.xml file and make whatever includes the calendar also include teh correct translation file. This way we can let the bvrowser cache the results of calendar-language.jsp for ever, and the calendar translation file (e.g. the calendar-de.js file) for ever as well.

      This will also remove the HACK#1 that was added from the code, without the need to upgrade atlassian-plugins.

        1. calendar-language.jsp
          2 kB

            Loading...
            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.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-13522

            Need to improve the way the calendar-<locale>.js files are served

            XMLWordPrintable

              • Icon: Suggestion Suggestion
              • Resolution: Fixed
              • 3.12
              • None
              • None
              • 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.

                After the JS and CSS improvements in JIRA 3.11 the calendar language translation file (e.g. the calendar-de.js file) is included from the calendar-language.jsp file.

                The problem is that if the user changes their language preference, until the cache expires, the wrong transaltion file will be served.

                Need to add all language files to the system-webresources-plugin.xml file and make whatever includes the calendar also include teh correct translation file. This way we can let the bvrowser cache the results of calendar-language.jsp for ever, and the calendar translation file (e.g. the calendar-de.js file) for ever as well.

                This will also remove the HACK#1 that was added from the code, without the need to upgrade atlassian-plugins.

                  1. calendar-language.jsp
                    2 kB

                        Unassigned Unassigned
                        anton@atlassian.com AntonA
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        0 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Estimated:
                            Original Estimate - 6h Original Estimate - 6h
                            6h
                            Remaining:
                            Remaining Estimate - 0h
                            0h
                            Logged:
                            Time Spent - 16h
                            16h

                              Unassigned Unassigned
                              anton@atlassian.com AntonA
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              0 Start watching this issue

                                Created:
                                Updated:
                                Resolved:

                                  Estimated:
                                  Original Estimate - 6h Original Estimate - 6h
                                  6h
                                  Remaining:
                                  Remaining Estimate - 0h
                                  0h
                                  Logged:
                                  Time Spent - 16h
                                  16h