Alex Expert

Hey @Mauricio Karas Thanks for sharing the endpoint for updating the portal announcement banner. I just want to add here that we can also update the Help Center banner using the following: * <baseurl>/rest/servicedesk/1/servicedesk-data/announcement/help-center Example cURL call: curl -X POST -u username:pass -H…

Hi @Tamas Salamon, and welcome to the community! The linking between Epics and other standard issues (Stories, Bug, etc.) is established by the Epic Link field on the standard issue. Therefore you might use these two methods to get it working: 1 - Create issues from the Epic Navigate to your Epic issue and hit Create Issue…

Hi @Melina Ailin Maquieyra and welcome to the community! If I got your question right, do you have a Scriptrunner Fast-track post-function working on a workflow transition in Jira Server and want the same to work on Jira Cloud? If that is the case I am afraid you will need to rewrite the code on the cloud workflow to…

Hi @Kevin I am afraid not, you can review what is included in all Cloud plans here Cheers, Alex

Hi @Margaret Hodges To clear the resolution field on an "In Progress" or "To Do" issue you can create a post-function on each transition of the workflow that is supposed to "clear" the resolution field. This article can give you some ways to implement that Best practices on using the "Resolution" field I hope it helps.…

Hi @Michael Milo Based on what you've described and assumed your project is a company-managed project, perhaps what is missing is adding the recently created custom field to the project's screens. Navigate to <YOUR_SITE>/plugins/servlet/project-config/<YOUR_PROJECT_KEY>/screens and verify the screens associated with your…

Hey @Soham Das Check out this link and play around with the permission properties https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status You might need to use a combination of them: * jira.permission.link.group=some-group * jira.permission.edit.group=some-group * jira.permission.attach.group=some-group…

Hi @Layssa Souza Give a try on the Tempo Configuration: * <YOUR_JIRA_SITE>/plugins/servlet/ac/io.tempo.jira/tempo-app#!/configuration/worklog-attributes Cheers, Aex

You might need to replace the properties to: * jira.permission.link.group=some-group * jira.permission.edit.group=some-group

Hi @Deeksha Srivastava The Sprint field is a system field that the Scrum Board uses to display the issues in the Active Sprint board. If you can see any Bugs in the backlog of the Scrum board you can drag and drop them to the active sprint. This will populate the Sprint field, and your Bugs will appear as expected on the…

Hi @Layssa Souza It makes sense now, apparently, the Tempo configuration has the Account as part of the Work Attributes. On my test site, I did not have it but I added to simulate:

Hi @Layssa Souza and welcome to the community. Yeah, you can remove the field from Edit and Create screens by navigating to <YOUR_JIRA_SITE>/plugins/servlet/project-config/<YOUR_PROJECT_KEY>/screens. If you keep the field on the view screen users will be able to see the value but won't change them. Cheers, Alex

Hi @Erica Warburg and welcome to the community! Your form at the end of the day is creating an issue in your Jira project. Therefore, you might need to review your notification scheme to make sure the right groups/roles are notified for the Create Issue event: Take a look at…

Hi @Soham Das I did a quick test adding 2 properties in the Done status and it prevented users from editing issues, attachments and links. However, comments are still available. I hope it helps. If this answer helps solve the problem, please come back and mark this answer as solved to help other community members with the…

Hi @DeAnna Law I managed to do something similar for a client by with a few workflow and screens trick: * Step 1: Creating a screen with all the fields that are "restricted": * Step 2: Creating a transition from Any Status to Itself and assigning the transition screen created on Step 1 Step 3: Create a Workflow Condition…

Hi @Deeksha Srivastava, and welcome to the community! Since you have already confirmed that statuses are mapped to the columns, and the filter includes bugs, I am assuming you can view those Bugs in the backlog of the Scrum Board. If that is the case, perhaps the missing piece of the puzzle is to assign the Bugs to an…

Hi @Trena Norcia The 500 executions per month threshold apply only to global rules on Automation for Jira. I recently made a review on my site and restricted the scope for many rules to be project rules, and it decreased significantly the number of execution per month. Cheers, Alex

Hi @Eric Brahmann If your site is in a free plan, Jira can send a maximum of 100 emails per day on the Free plan, then email notifications will be paused until the following day. You can have an idea at What is the Free Jira Cloud plan? By any chance have you reached this limitation? Cheers, Alex

Hey @Masa Janezic Happy to hear that you figured out the mystery. Even happy that I also learned a piece of something from this, thank you! I enabled the same dark feature on my Jira and it all makes sense now. I am still using the description trick I mentioned before. See how Jira stores the information when 1 option is…

Hi @Masa Janezic It's funny, but I have a pretty similar script on a test environment, and it works as expected. I changed the custom fields id's to use your example, and it still works. //customfield_12103 = multi-select //customfield_12100 = checkbox field //I want the checkbox field to apear only if the multi-select…

Hi @Andre Menezes I am not sure if I got your scenario wrong, but apparently, Jira calculates sub-task and displays them in the standard issue (Task, Story, Bug) by default. See the snippet below from my instance: Unless you have a different requirement, you could leverage this feature. Cheers, Alex

Hi @Carolyn Based on the scenario you described, it seems that the groups of users is lacking global permission to Browse Users and Groups. Navigate to <YOUR_JIRA_SITE/secure/admin/GlobalPermissions!default.jspa and review users/groups that need to have this permission to browse other users. Cheers, Alex

Hi @Mr_ Snrub I believe you can get around this use case with the following rule: Cheers, Alex

Hi @Richard Morgan If you are referring to the Send email feature in <YOUR_JIRA_SITE>/secure/admin/SendBulkMail!default.jspa I am afraid you cannot change the sender of the e-mail. However, if your e-mail is sent from a JSM project you can change the project's e-mail…

Hey @Taranjeet Singh and @Colton_Kosicek Thanks for pitching in with your suggestions, I loved the engagement 😃!! Yeah, we definitely make the JQL better by adding the statusCategory as "To Do" to both suggestions, actually I have already done that. But even though, I am positive that resolution is the way go to, we need…

Hi @Agnieszka Santos Just a quick reminder to help the community. If this answer helped to solve the problem, please come back and mark this answer as solved to help other community members with the same challenge. If not, you are welcome to share your solution as well. Cheers, Alex

Hi, @hisham Osman; welcome to the community! I am afraid you cannot get this result from Jira "out-of-the-box" in a scalable way. But if you have the issue key for each epic, your JQL would be something like: project = "YOUR_PROJECT" and type = story AND (statusCategory in ("In Progress", "To Do") or resolution is empty)…

Hey @Masa Janezic I am glad you've got some progress on having the behaviour script working for your use case. The reason why it does not work when the page first loads is that you need to ensure that this script is triggered by adding it to the Initialiser section of the behaviour, along with the same script in the field…

I @Larry Peery I might be missing something, but given that the attachmentNames variable has only the "temporary" attachment uploaded during the transition you might not need to count those with the name "temp". Based on your input the attachmentNames variable seems to be an array, therefore I"m pretty sure to can try the…

Hi @Masa Janezic, and welcome to the community! I think this modification might do the job: //customfield_12103 = multi-select //customfield_12100 = checkbox field //I want the checkbox field to apear only if the multi-select field contains "FreeRounds type" option. def dropDown = getFieldById("customfield_12103") def…