Gor Greyan Expert

Dear @Ram Kumar Aravindakshan _Adaptavist_ , Thanks a lot, it works.

Dear @Ram Sharma If it the Team field is Select List field, you can input Fly and Samsung values into it, then create an automation. Trigger - When issue is assigned to a user If/Else block - Condition, if Assignee is user A Action - Edit Issue field Team and select option Fly. Else block - Condition, if Assignee is user…

Hi @Youmna Alomari , Thanks for the great question. As I did research, Jira can't auto-create a Kanban board when creating a new Jira project. Boards are tied to filters, and those filters are typically specific to a project.

Hi @Razia Allen Seems the action type for the Start sprint is not available in the Cloud. There is an open task for that feature. https://jira.atlassian.com/browse/JRACLOUD-90921 Also, you can have a look at this community discussion.…

Hi @Ram Sharma , Please provide the type for the Team field, on which it should be autofilled.

Dear @Ram Kumar Aravindakshan _Adaptavist_ , The result is that it allows me to create the ticket, despite the fact that I choose the date, for example, 2030. I mapped it with my field which is To field.

Hi @Ram Kumar Aravindakshan _Adaptavist_ , Thanks for the provided example, I set it and mapped it with my field, but still it allows me to open a ticket, while setting it to a greater date than a year.

Hi @Derek LoGrande Try the following smart value. {{issue.comments.latest.body.replace("[Attachment:.*]", "")}}

Hi Dear @amal Abdallah You can put a post function on the workflow that ensures the sub-tasks take on the parent's security level after the issue is transitioned. Here's how you do it: Go to the Workflow editor. Select the transition that creates a sub-task. Include a Post Function that alters the sub-task security level…

Hi @Ram Kumar Aravindakshan _Adaptavist_ Did you manage to check my answer?

Hi @kat Am I right that CustomField should contain the existing projects in Jira and not to enter values into it?

Good Evening @Digvijay Singh Gehlot I didn't get the second condition well about the Checkbox. Is it customfield, and is it present only in the parent issue? You can try automation like this. First. Trigger --> Issue Transition Condition 1 --> Checking the parent issue(In my example, it is Story) Condition 2 --> Checking…

Dear @Fahad Can you please check the roadmap configuration? Your roadmap might be configured to use a tracking method(e.g., Story points, time estimates, or issue count) that doesn't match the data in your issues. You can check this in Roadmap Setting ---> Progress Tracking Method.

Hi @Mitesh Shah Could you please share Audit Log from the automation, for that Test ticket?

Hi Fahad, Could you please share a screenshot, how it is being shown?

Hi Ram, Yes, my field is Custom Date Field. I want to put that behaviour in the create screen, when choosing the date from that field, it should not allow to select date greater than one year.

Any updates dear colleagues?

Dear @Felix Leung Did you check the advanced roadmap permissions for that user?

Dear @thumuluru.shreya In the workflow for the specific status, try the following properties. jira.field.*field_id*.readonly = true

Hi Dear @Felix Leung Do you user Data Center or Cloud?

Hi Dear @Heather Driscoll Try the following, it should be worked. "labels!= v8_testing_needed or labels is Empty

Hi @sanjjoy rio Please try the following JQL. issue in hasAnyLinks("summary ~ xxx") and issuetype = Epic I have Scriptrunner Add-on, I think It comes from that or from another plugin, as Jira doesn't have built-in the mentioned function.

Hi, Dear Tinker, Yes, I have already opened a ticket on their support.

Dear @Radek Dostál It worked. Thanks a lot!

Hi, Dear @Radek Dostál Thanks for the provided script, it worked for the create screen, but from the Customer Portal it is not working, but I did mapping with the issue type. Please advice.

Hi Bharat, Thanks for the answer, but it didn't work.

@Kseniia TrushnikovaThank You very much, it works.