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,456,123
Community Members
 
Community Events
176
Community Groups

structured project information in Team central?

I am frequently working with customers who want to collect specific information on a project level. Things like customer, country or region, volume, ...

My standard approach is defining an issue type in Jira to collect all this metadata. But this solution has its limitations, e.g. that there should be only one set of meta data per project.

Could Team Central become a place to collect project metadata? This would require the ability to define custom fields on a project level.

1 comment

Mary Raleigh Atlassian Team May 03, 2021

Hi @Arnd Layer , great question! In fact I'd argue that a key differentiator in Team Central, compared to more free form ways of communicating project status, is our structured dataset. The current metadata we capture for your project includes:

  • Status (On track, At risk, Off track) by week
  • Project contributors 
  • Target date (and when/how many times that date is changed)
  • Goal the project contributes to
  • Dependency relationships to other projects (dependent on, depended on by)
  • Count of followers
  • And of course my favorite, labels that allow you to capture programs 

Screen Shot 2021-05-03 at 11.42.13 AM.png

Today, labels offer the best way to organize groups of projects and goals by the categories you have listed above. 

Screen Shot 2021-05-03 at 11.44.07 AM.png

Adding a label to any goal or project enables a custom view of all projects and goals with those labels. The custom view includes:

  • Count of people allocated across each project
  • Summary of projects by status
  • Summary of goals by status
  • A high level roadmap view
  • And a summary of completed and paused projects

In the future we may offer more custom fields, possibly as part of a paid tier. Would you be interested in participating in our pricing research to help us understand how you value custom fields in Team Central and share more of how you would use it? If so feel free to reach out to me at mary@atlassian.com!

Like # people like this

Thank you, @Mary Raleigh for your comments. I am looking forward to what's coming in Team Central. Surely, it is hard to find the balance between customisation options and not making the product too complicated.

As a consultant, I am primarily considering what would be required to create something to our customers that brings value to them. And this is always based on how they work today. And I am sure that most of them today would ask for some predefined taxonomy in addition to label based folksonomy. Also, numbers will not make sense in labels.

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events