Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Next Gen Project - how to import or update ticket Creation Date Edited

Question: Is it possible to import (or modify) the Ticket Creation date for tickets in a Next Gen project? From what I can divine, it appears that the answer is "no".

 

Here is what I'm trying to do:

1. I have a CSV file that contains data from an old Issue Tracker that I want to migrate into a next gen project.

2. I imported the data into my next gen project from the Search Results > ... > Import Issue from CSV. => This importer did not allow mapping the Creation Field, so all tickets wound up having creation date = the day that I did the import.

3. Attempt to update the Creation Date using the System - External Import. This does allow mapping creation date. => Unfortunately this fails. It appears that the System External Import does not support Next Generation projects.

 

Possible work around:

1. Create a Custom Field to hold the "old" creation date. => This is not a good solution as it means I then have to implement logic (automation) to set this value for any NEW tickets that get created in the project. It also means I'll have to maintain two separate fields for the ticket's creation date for the life of the project. This is not very usable from an actual "user's" perspective for the project.

2. Give up on using Next Gen and redo using the "old" style project. => This should work but means having to redo project configuration, automation, etc. And there's no guarantees that everything I have configured/implemented is actually possible with the old style project. i.e. What trade-offs are there with going back to the old style project?

 

1 answer

Hi @David Prescott,

I think going with classic is going to be your best bet indeed for this scenario. If you really want, you can migrate your imported data from classic to next-gen afterwards if you have good reasons for that.

You can find a comparison between both project types from this overview page.

Regarding your question about trade-offs, definitely have a close look at this page on migration between next-gen and classic. It has a very clear overview on things to consider during that migration - both ways.

As a rule of thumb: keep in mind that next-gen projects were designed with simplicity of configuration in mind. As a consequence, they are designed to be used as standalone projects. If you are thinking about reporting across multiple projects or collaborate on them with multiple teams, I'd recommend to stick with classic.

Hope this helps!

kr,

Walter   

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,073 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you