Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Additional Field Types

I have a Project that works perfectly for the broad team - Call it Project Blue. I am onboarding vendors who should not have access to everything in Blue.

My plan was to create a new project, Red, and clone issues from Blue --> Red for vendors to work. However we are stumbling in that:

  1. I cannot copy/clone/import settings from Blue to Red in next-gen
  2. I cannot re-use an Issue Type from Blue to Red; it looks like a need to rebuild the entire issue type in Red.

Anyone have good workarounds or suggestions?

1 answer

0 votes

Hello Paul,

Thank you for getting in touch with Atlassian Community!
Next-gen are independent projects, so all the settings are specific for each one, so if you create issue types, custom fields, it won't be available for any next-gen or classic projects.
Please, check the article below to find more information about next-gen projects:
- Everything you want to know about next-gen projects in Jira Cloud

Regards,
Angélica

Hi Angelica,

Unfortunately this really breaks things when I need to have some people work in one project and some in another.

1. It's hard to know which project a field is coming from in Issues and views.

2. I now need to replicate settings

3. There is no way to easily copy one item to another project as the fields don't get copied.

I know the goal is a simple tool for next-gen but given the lack of permissioning this makes it very difficult for complex teams.

Like Angélica Luz likes this

Hi Paul,

Thank you for your feedback!
For now, we must wait for new features to be implemented on next-gen and you are more than welcome to share your ideas as feature requests on jira.atlassian.com.
You can check the sub-tasks on the feature JSWCLOUD-17392 which has all ideas for next-gen projects.
Also, we have a roadmap showing the features that are being developed:
- Next-gen roadmap for Jira Software Cloud

Regards,
Angélica

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Team-managed projects

4 steps to get actual statuses on the Jira board.

Jira   is a powerful tool   that helps teams to plan, manage, and report on their work.   We love using Jira, especially for its ability to track issue progress. But how to monitor the...

1,174 views 10 14
Read article

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