Comments
-
I kind of thought that's what you might see. Maybe delete the URL back to where this is the end of it: cb-jira-automation-rules#!/ You probably have the project tacked on to the end.
-
You sound like my wife when I fix something around the house without burning it down. hahaha. You are welcome. I am sorry it took so long to get you to a solution. :-)
-
Hi @Harry Bob - Is it just one particular status that you need the notification for? What about: project = ABC and status = "Open" and status changed to "Open" before startOfDay(-5)
-
Hi Hema - Welcome to the Atlassian Community! Are you using an add-on app? Can you show a screenshot of your post function?
-
Totally up to you, but what you will find is that Next-gen is very simple to use out of the box. But next to impossible to modify/customize it to get what you want if you need changes. Classic Software projects are a little more involved but there are LOTS of ways to customize it. I exclusively use Class projects. :-)
-
Hi Patrick, I would think you should see those. Are you starting from a particular project? Or from just the main Rules menu? Can you include a screenshot of what you see?
-
Choose the Copy From option from the three dot menu on the right.
-
Your syntax is wrong there. I think I would rather do an Edit issue component instead of Assign the user. Then you can edit the Assignee field to copy from the QA field. If that doesn't work out we can go back to the this option and work out the syntax.
-
Ah, sorry - you are using a Next-gen project. So yes, you would need to create a new custom field for that. But Next-gen projects use a different scheme for connecting to Epics so not real sure if all of that will work.
-
Sorry - I meant the details of the Rule itself - for the Then Assign issue to component.
-
Sure. 1. Is the Filled Positions a number field? If not you will need to create a new one that is. 2. Create an Automation For Jira rule that adds the value of 1 to the Filled Positions field based on when an issue moves into the status. a. Create a rule for when an Issue Transitions b. Select the status you want to…
-
I hope that helped a little.
-
Hi Donata, How boards prioritize issues is very complicated and always seem to be a mystery to me. There seems to be some type of correlation as to when the card comes onto a board. But if you manually change the prioritization of an issue on one board, it absolutely will not change it on another board using rank. Bottom…
-
No need to create a new field - it will be there. You might need to add the Component field to the screen you are using. But you should also see Components listed on the left hand navigation while on a board. You must be a Project Administrator to add new Components and Components are unique to each project. So if you want…
-
Hi Paul - Welcome to the Atlassian Community! There are several ways you can approach this. 1. Add yourself as a Watcher to the issue. Then check the Notification Scheme attached to the project to see when the Watcher gets notified for each action. 2. Add an activity stream gadget to a personal dashboard. Use a filter that…
-
Probably so. Can you share a screenshot of the details of when you are setting the value of the field?
-
Hi @Jean-François RIOU , Do you have Automation For Jira? I just accomplished that same thing this weekend with the Cloud version.
-
Great! Glad you were able to figure it out!
-
Hi @Jean-François RIOU , Do you have Automation For Jira or ScriptRunner? It could probably be done with one of those, but I do not use ScirptRunner so I could not offer any advice there.
-
Hi Prabhu, You might could do an Automation for Jira rule to increase or decrease the number each time an issue moves into or out of the appropriate status where the count is being done.
-
Ah, so you want THAT message to show to the user? You can't do that with Automation for Jira. You would be better off adding a Validator on the transition in the workflow and give the error message there.
-
Hi @vshah , Are you able to assign the issue to the user doing it manually? It looks like the user you are trying to assign the issue to by Automation does not have that permission. You can verify with the Assignable User permission in the Permission Scheme attached to the Project.
-
Hi Prashanth - Welcome to the Atlassian Community! You should be able to do that with an add-on such as JMWE or ScriptRunner, which you have. Can you share what you have already for the Validator? @Nic Brough -Adaptavist- - Any idea?
-
You are not going to be able to do that with a single Validator unless you are using something like JMWE or ScriptRunner. The other option is to create to separate transitions from Backlog to To Do and put a condition on each to to make the Issue Type (one for Bug, one for Story). Then you put the validator on the…
-
Hi Darren, What kind of error message are you wanting to display? Automation for Jira does not do conditions or validations, it only performs the function after something else has happened.
-
Hi @vlad - Welcome to the Atlassian Community! You will need a second rule to handle number 3. You should use a rule based on a Transition change.
-
Hi @Leisa Reichelt , It's been a little over a month since your last post. Is there any update you can share? Thanks! John