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,556,386
Community Members
 
Community Events
184
Community Groups

Sum custom fields without automation

Hi there,

I have looked around and most of the articles explain using Automation for sum up different custom fields. I have 5 different custom fields that I want to sum up so I can see which ticket got the highest numbers so we can prioritize e.g. These fields will contribute different rating and the reporter only need to give rating between 1-5 then base on this value, it will calculate the %. I am sure its possible in Automation but wonder if I can do without it or not using any addons?

Any suggestions are welcome :)

  1. User Impact and Business Impact combined - 40%
  2. Technical Debt and Complexity combined - 30%
  3. Risk - 10%
  4. Customer Requests - 15%
  5. Dependencies - 5%

1 answer

1 accepted

4 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 26, 2023

Hi @Mimi Peters 

From what you describe, you can do that using the built-in math operations for automation rules, as described here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/

Kind regards,
Bill

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 26, 2023

Further to what Bill has provided here, to answer your question as to whether this can be done without Automation or an addon the answer is no. I'm unsure why you may be adverse to an Automation rule.

Thanks both.

The automation rule is great, as we have a monthly limit usage so I am trying to avoid using up the quota that's all :) 

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 26, 2023

You can set up project specific rules which are unlimited. If you use the rule on multiple projects then global is easier but per project can work too.

Like # people like this

Hi Jack, 

Would you mind to interpret more? How do I set so it will be unlimited? 

the above fields can be used by 5 projects and what is my steps to achieve these? 

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 26, 2023

Hey @Mimi Peters - Any rule that runs against a single project has unlimited executions at no cost. It is only rules that run against multiple projects or global rules (no projects identified) that count against your rule limitation. 

Like # people like this
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 27, 2023

Yes what John said. Basically you would create the rule in one project then copy it and use in each of the other 4. So you end up with 5 rules, one for each project. The downside is you have 5 rules to manage.

Like # people like this

wao, I did not know that great many thanks for this tips :) 

Like John Funk likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events