Nir Haimov Community Champion

Hello @TheGloryDay Check this documentation, this should work (even if the jql shows red line like it does not recognize what you are writing) https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-development-fields-reference-973491363.html

Hi @Santosh Singh Can you be more specific? What you are trying to do and what is not working? what is happening instead of what you really wanted to happen? Screenshots may help too

Hi @Pallavi Deore Follow the API documentation, everything you need regarding API is there: https://docs.atlassian.com/software/jira/docs/api/REST/8.13.0/#api/2-getPermissions

Hi @mini trivedi I don't know which package you use, and i don't use python, but i do know from other people that jira python package changes many times, and things that used to work before now not working, that's because the python package changed, so you need to go to the package documentation and understand what was…

No problem :) According to the documentations, The following functions can be used to convert a date to a date with a time component: {{now.toStartOfDay}}{{now.toCurrentTime}}{{now.toDateTimeAtStartOfDay}}{{now.toDateTimeAtStartOfDay(timezone)}}{{now.toDateTimeAtCurrentTime}}{{now.toDateTimeAtCurrentTime(timezone)}} Please…

@Sam Lander can you send screenshot of the automation, so we can see exactly how look what you wrote?

Hi @Sam Lander Try ".toDateTime.as("yyyy-MM-dd HH:mm") Try first to print it to the automation log, see if you get the result you want, then try to set it to a field. Note that in order to set it to a field the format must be exactly as your dateTime customfields look like, make sure if you need use "-" or "/"

Hi @Peter Chodakowski Can you recreate your automation here: https://www.atlassian.com/software/jira/automation-template-library/rules#/labels/all/customLabelId/1453 ? And share the link to your rule, it will be easier to see what you did and try to help

Maybe you are right, Last time i was in a discussion like that, i remember that the conclusion was as i told you (from the JAVA API side), maybe as you said, from the public API there is a way to do it, i didn't check so i can't tell

Hi @Suvarna Arigela I didn't understand, you ask for a solution, then you give 2 options you created that seems to solve your issue... So what else do you need?

Hi @Krishna Teja Medam Personally, i don't like to work with any of the libraries, just use "requests" and write simple API calls, that should work perfectly without breaking your mind on whats wrong with the library or with what you do wrong...

Hi @sm.park , In which cases your script fails? In which line it fails? Can you send your actual script and point which line code is failing?

Hi @Alexander Raymukanov You didn't find any documentation to set Rank because there is no way to do so. Rank is a system field that it's actual value is encrypted and not human read. I know in the tickets in the UI you see numbers for Rank, like : 1, 2, 5, 9... But behind the scenes, each number will be some complex value…

Hi @A_lis I tried with Automation for Jira and found it a bit complicated (or even not possible), but with ScriptRunner it is possible, i will give you the direction and hope you will managed from there: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.Issue import…

Hi @smhf97 Try this: import net.java.ao.schema.Unique;

Hi @A_lis You want the email will be sent automatically when all related tasks are done? If yes, you did it wrong. What you did is a transition, that once you click on it (in the issue view) it will check if all related issues are done, and if yes, it will send email... so the email is based on your action to click the…

Hi @Shireesha Baddam That's right, in the documentation i sent you there is another topic for handling dates: https://support.atlassian.com/jira-software-cloud/docs/smart-values-date-and-time-functions/ So, all you should do is like this: {{issue.fixVersions.releaseDate.jiraDate}}

Hi @Shireesha Baddam It is possible using {{issue.fixVersions.releaseDate}} You can read more about it in the documentation https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/

Hi @Manh Tuan Do Assuming you are using Jira 8.0.0 and above. Here is a working example: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.jql.parser.JqlQueryParser import com.atlassian.jira.user.ApplicationUser import com.atlassian.jira.web.bean.PagerFilter import…

Hi @Nandhini kandan , Please open new question and tag me, i will help you with pleasure, it will be easy to track new question with new relevant topic. Also, in the new question, please add screenshots with what you did so far. Thanks.

Hi @alexander_dvorkin Use this for version: fixVersion not in (1.0.0, 1.1.0, 2.2.0) And use this for dates: fixVersion not in releaseDate("on 2020-12-31") You can google for "jql release date" for more dates example 

Hi @Deepan Kumar Raghavan Vasu Basically yes. * uninstall the add-on * go the to add-on page on the Atlassian Marketplace, click on "versions" tab, and download manually the version you want * go to jira add-ons page, and click to upload add-on manually, and select the add-on you just downloaded.

Hi @Vidhya Mohan Please check Jira admin settings if maybe HTML support in custom field description turned off.

Hi @Sebastián Campos Your code is nothing like the code in the tutorial... And your annotations are wrong. Also, what UserManager are you trying to use? Please specify the entire library in your import Thanks.

Hi @Vidhya Mohan Like this: (function ($) { AJS.toInit(function () { // init on load var issueTypes = ["Test", "Test Plan", "Test Set", "Test Execution", "Pre-Condition"]; if (issueTypes.includes($("#issuetype-field").val())) AJS.$("#qf-field-picker-trigger").hide(); }) JIRA.bind(JIRA.Events.NEW_CONTENT_ADDED, function (e,…

@Vidhya Mohan try to put this line: var issueTypes = ["Test", "Test Plan", "Test Set", "Test Execution", "Pre-Condition"]; Also inside "Jira.bind" before the "if" statement

I understand, but i need you to open the browser dev tool (click F12) and see if there are errors that cause your create screen to not show (as you sent before)

Hi @Vidhya Mohan Check for errors in the dev tools and let me know

Hi @Vidhya Mohan Exactly :)

Hi @Vidhya Mohan Does all your "test" issue types, are under the same field configuration?