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

Project Automation Not Working

Hi there,

My automation doesn't work. It shows:

This rule was configured with a project restriction. You can change this restriction in the 'Rule details' section. Only issues from the following projects or project types will be considered: ORD

What's the meaning of it? How to fix this issue?

 

Screenshot_2.png

2 answers

Hi @Yvonne Wan ,

It means the rule will run in only selected projects, in other words, it is restricted to particular projects. BTW what are you trying to achieve?

Cheers, Kevin.

Hello @Kevin Johnson ,

Thanks for your answer.

1. What I want is to link the status of issues to that of the epic.

For example, there are around 15 tasks under an epic. I pre-set 15 epic status from status A to status O.

If the status of the first issue - Collect Information -becomes DONE, then the status of the epic will become A. 

If the status of the second issue - Received Product - becomes DONE, then the status of epic will becomes B.

If the status of the third issue - Assign Project to a specific Coordinator - becomes DONE, then the status of epic will becomes C.

.........

2. Another thing I want is to assign a specific assignee to the third issue automatically if the status of the second issue becomes DONE.

 

Screenshot_3.png

Like Kevin Johnson likes this

@Yvonne Wan Try choosing the Epic parent issue as you're trying to update that, and not a normally linked issue.

I'm attaching this picture for your reference, try something like this.

p4.PNG

0 votes
John Funk Community Leader Apr 27, 2021

Hi Yvonne,

The message you highlight is just a general warning, and not necessarily an error. If all of the Epics and issues you are working with are only in the ORD project, then you are fine. 

The part that did not "work" is that the branch found no related issues for issue ORD-603. Meaning that particular issue was not linked to another other issues using the "is blocked by" issue link type. 

Can you share a screenshot of ORD-603 and the issues it is linked to? 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

254 views 2 1
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