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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,281
Community Members
 
Community Events
176
Community Groups

Reinventing the wheel?

As I'm starting to use Portfolio, I've noticed that in a number of places (like dependencies, start/end dates, etc) Portfolio is creating a net new implementation that is not connected to existing fields & settings in JIRA. Is that intentional? Is there a desire to break with that implementation or is this a step along the way that will be remedied later?

1 answer

0 votes

Hi @acarter

It depends on the field and the configuration - for example:

There are some variances - such as Target Start not naturally mapped to a Start Date field. But it depends on which fields / resources you're referring to above.

If this doesn't answer your query - let us know more information and what hosting type you have (Cloud / Server / Data Center) :)

Ste

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events