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,365,201
Community Members
 
Community Events
168
Community Groups

Best way to collect information from all issue team members with JIRA having no table inputs?

Hi all,  I need to collect data that looks like.

Name

Role

Time spent in preparation

Continuing Team Member

Jim Smith

Systems Eng

10

N

Jane Smith

Elec Eng

30

Y

John Smith

Safety Assessor

4

Y

Mary Smith

Software Eng

24

N

 

With a possibility of up to 10 members on the team.  This is collected for every issue and is needed to compute metrics

 

Member 1 ______________________________ (user picker)

Start typing to get a list of possible matches.

Member 1 Hours  __________

Time spent in preparation

Member 1 Continuing Team Member _______  (Yes/No Radio Button)

Continuing Team Member

Member 2 ______________________________ (user picker)

Start typing to get a list of possible matches.

Member 2 Hours  __________

Time spent in preparation

Member 2 Continuing Team Member _______  (Yes/No Radio Button)

Continuing Team Member

 

...  Up to 10

As you can see this gets really ugly really fast.  especially if you want to add a description to each field. Especially if you want a description or use the built ins like User picker which always give you a description.

I know Confluence has tables,  but then how do we pull it back in to include in our dashboard metrics?

There must be a better way!   

The thought of manually going in and creating 30 new custom fields,  configuring them, adding defaults, adding them to the screens,  adding required setting to get rid of None on the radio button....     And this is our sandbox server,  everything will have to be repeated, on the production server.

Thoughts,  suggestions?   And  a plugin won't work.  We have already purchased a number of plugins and management is getting tired of us telling them "you can get what you want,  you just have to buy the plugin"

1 answer

0 votes

I would create a sub-task for each person.

Thanks for the reply,   That doesn't really work, we need the data to be available for filters in sorting at the parent level.

I have just done it the manual painful way..

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events