Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-64812

JIM does not respect the comment timestamps

    XMLWordPrintable

Details

    • 7.04
    • 1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 06 September 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 06 September 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

    Description

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      I ran up JIM on JIRA 7.1.0-OD-02-025

      I followed the docs on CAC and the "help suggestions" in the importer itself to have comments that retain their "created date"

      My csv looks like

      Summary, Assignee, Reporter, Issue Type, Description, Comment, Comment
"Test issue 1", admin, admin, 1, "Issue Description 1" ,  "01/01/2012 10:10:00; admin; This is comment 1"
"Test issue 2", admin, admin, 1, "Issue Description 2" ,  "01/01/2012 10:10:00; admin; This is comment 2.1", "01/01/2012 10:12:00; admin; This is comment 2.2"

      however the comments get created as JUST now instead of in 2012

      I get a comment like

      I did not change the suggested JIM date formats at all and left them as

      dd/MMM/yy h:mm a

      The suggested help text from JIM does NOT match the actual format

      To preserve the comment author/date use format. E.g. "05/05/2010 11:20:30; adam; This is a comment."

      ^ this is what JIM suggests when importing.

      I then changed the data to have the AM/PM indicator as suggested but it still does not work and I get the same result.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-64812 JIM does not respect the comment timestamps

          • Medium - Medium priority issues
          • Closed
          is duplicated by

          JIM-1691 Loading...

          Activity

            People

              Unassigned Unassigned
              kkolonko Kamil Kolonko
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: