Piotr Zadrożny _Eyzee_ Community Champion

Hi @Darrian Castillo As far as I know, you can't copy the automation rule component - but you can use JSON to provide field configuration. Please take a look at this documentation: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/, it should clear things out. Best, Piotr

Hi @Zincy Welcome to Community! You can transition multiple issues at once using the bulk change feature. Here you can find out more about that topic: https://support.atlassian.com/jira-software-cloud/docs/edit-multiple-issues-at-the-same-time/ To sum it up: * Perform a search with the required filters (eg. status =…

Hi @sharath kalappa Welcome to Community! This error message indicates that you don't have a properly configured PostgreSQL server. In PostgreSQL there is a file pg_hba.conf that control from which computer, which user can connect to which database. You are trying to connect to the PostgreSQL server from 192.168.1.7 using…

Hi @Jess Thornberry ,if this answer helped you, please mark it accepted to help other users find it.

Hi @Alex Li, if this answer helped you, please mark it accepted to help other users find it.

Hi @Ryuichi Sugimoto Welcome to Community! In Jira you can assign single person to single issue. This assignee can change during issue lifecycle. This configuration is by design and it helps to reports on work assignment, work estimation, work performance,... If you would like you can add additional custom fields "User…

Hi @Iqbal Mann You can modify your e-mail templates. To do so go to Project Settings -> Customer notifications -> Edit templates Then in CSS tab add at the bottom: .myButton { background-color:#ff8c00; display:inline-block; cursor:pointer; font-family:Arial; font-size:10px; color:#ffffff; text-decoration:none; padding:6px…

Hi @Fred Gallegos Welcome to Community! When you claim accounts they will become Managed Accounts, which means you will be able to edit, delete, or deactivate those accounts. You will be also able to apply security policies to your managed accounts (using additional software Atlassian Access) like requiring users to use…

Hi @Jess Thornberry Welcome to Community! You can search issues using the JQL query: summary ~ "jessica" You can read more here: https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-fields-reference-939938743.html#Advancedsearchingfieldsreference-SummarySummary Best regards, Piotr

Hi @Jack Brickey , Please correct me if I'm wrong but I believe that your condition can include more issues that is needed. For example if 70 days ago issue will transition to Awaiting Resolved Approval and than 65 days ago the Client will make "Client Declined" transition. Then after 60 days (5 days ago) the issue will be…

Please also verify if you are using untranslated status names. Maybe on your workflow you are not using Resolved status (maybe its just translated to Resolved due to your selected prefered language). I believe you can find untranslated status name used in this workflow by clicking View workflow inside issue.

Hi @Andy Greenwood , Can you show us workflow conditions and validators on your "Client Approved" transition? Maybe you have some requirements that your rule/actor does not meet. Futhermore please verify if your rule actor has neccessary permission to make such transition (min. browse project, transition issue, maybe…

Adding to what Belto already said, it can also be: * jira automation rule that trigger such behaviour (you can verify it in Project Settings -> Automation) * post function on Create issue transition in workflow associated with that project (check…

Hi @Alex Li If you need only issues which updates to Accepted during that period, you can use following JQL query: status CHANGED TO accepted DURING ("2022/01/01", "2022/03/31") On the other hand, if you need all issues that were in accepted status during that period (not only those that was changed to this status during…

Well already corrected. The proper second rule should look like this: BTW. To create automation rules you need to be Project Administrator. To create one just click Project settings -> Automation -> Create rule. Best regards, Piotr

Hi @Stuart Cross Welcome to Community! You can create automation that will meet your requirements. Regarding first question you can create automation simmilar to following: Regarding your second question you can create new Version after releasing existing one using rule simmilar to following. This rule will create new…

Hi @Echo Yang I am not sure if I get it correctly. If you would like to add specific watchers to every single new issue that meet specific criteria like Priority, you can create rule simmilar to following: Best, Piotr

Hi @Кирилл Матвейко You are missing branch component to your rule (without it Jira Automation does not know to which issues change priority): So: Trigger: Sprint Completed with selected Board Branch rule / related issues: Issues in the sprint Inside that branch: * Condition: depending on your configuration you can select…

Hi @Emin Sharifov Welcome to Community! I'm guessing you are asking in regards to Jira Cloud version... Advanced Roadmaps is a feature of Jira Software Cloud Premium. To begin using Advanced Roadmaps in Cloud you need to upgrade your Jira from Standard to Premium plan. Best, Piotr

Hi @Paul Efford Your Jira admin should prepare project configuration for you, based on your requirements. You just don't have sufficient permissions to do so. I cannot suggest you proper configuration regarding workflow, fields, screens because you provide too little details on that matter. All of those configuration (also…

Hi @kamlesh.patel Employees that require only access to the customer portal to create new requests do not require any license. Agents who will work on customer requests and resolve them do require valid licenses. You can read more about it…

Hi @John Sanchez Sr You can just move all of the created issues from the new project to the correct one. You can use the bulk move feature to move all those issues at once. You can read about it…

Hi @WasimBuden Have you checked the last proposed version? In my tests it works as intended ( "type in standardIssueTypes()" added in each version just to limit created issues below 1000+) : * Static version: * Dynamic version 1: * Dynamic version 2: Best regards, Piotr

Hello @WasimBuden Did the proposed solution help? If so, please mark it accepted to help other users find it. Best, Piotr

Well, I have just verified and when you impersonate someone's account you can visit her/his customer portal if only this user has also a regular Jira user account (not only a JSM customer). In community thread you have linked, there is a need to impersonate someone with only customer portal access permission which as far…

Hi @Sam Ayres It's still possible - you can find this option in users management after clicking ... near selected product.: Best, Piotr

Hi @WasimBuden Of course, you are right. From startOfWeek() official documentation: "this function considers Sunday to be the first day of the week". So it should be: created >= startOfWeek(-8310m) AND created <= endOfWeek(-8310m) or created >= startOfWeek(-8310m) AND created <= startOfWeek(1770m)

Hi @Dan Anas Welcome to Atlassian Community! To alter the Target project you need to create Global automation rule. You can do it as Jira administrator in System -> Global automation. Keep in mind that there is a limitation in execution of global rules per month - read more…

Hi @Dan H You can create rule similar to following: Make sure to check "Allow rule trigger" in Rule details to allow rule created by you (the one that transition story) to trigger this one.: Best, Piotr

Hi @kanaka prasad ponnuru There is no built-in way to accomplish this. You can use workflow condition or validator provided by 3rd apps like JMWE (Linked Issues Condition/Validator) or write your own custom script using app like Scriptrunner for Jira. Just to differentiate between condition and validator: Conditions…