Uploaded image for project: 'Jira Software Server and Data Center'
  1. Jira Software Server and Data Center
  2. JSWSERVER-15936

JIRA Import from Trac fails to handle Trac tickets with multiple owners or reporters

    XMLWordPrintable

    Details

    • Introduced in Version:
      7.03
    • Support reference count:
      1
    • Symptom Severity:
      Severity 3 - Minor
    • Current Status:
      Hide
      Atlassian Update – 12 February 2020

      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,
      Jira Server Bug Fix team

      Show
      Atlassian Update – 12 February 2020 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, Jira Server Bug Fix team

      Description

      Summary

      JIRA Import from Trac fails to handle Trac tickets with multiple owners or reporters.
      Trac allows tickets to be owned or reported by multiple users.
      JIRA importer fails to handle those tickets

      Steps to Reproduce

      1. On Trac create tickets with multiple owners.
        database shout look like this:
        Here's an example SQL query (select owner, reporter from ticket) from TRAC database:
        owner | reporter
        ---------------------------------------+---------
        user1, user2, user3 | user4
      2. Import trac to JIRA.

      Expected Results

      • JIRA should create the corresponding ticket and have the ticket assignee set to user1.
      • user2 and user3 should be created.

      Actual Results

      JIRA creates a user as "user1, user2, user3" and have him assigned to the ticket.

      Workaround

      • remove the wrong user manually and recreate the users manually.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            sabdelfattah Sherif Abdelfattah
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: