Nir Haimov Community Champion

Hi @Vidhya Mohan I tested it and it works fine for all issue types. Where did you put your script?

Hi @Junseok Lee I found the following answer from an Atlassian Team member in another post: @Scanned says, consider this class as part of something that the spring-scanner build time should consider (like @Component / @Inject but without any other side effects). For the record "rest modules" are magic in that they do not…

So seems like you answer to your-self :) Seems like the fast-track not performing the post-function script (and maybe all other post-functions you have in this step)

Hi @Ashutosh Shrivastava Sorry, but i can't help you that way, you need to access the original code (and not the package from the JAR). There you should have only 1 pom.xml, main folder with all classes, resources folder with all resources (js, css, etc...) You are trying to work on the wrong files. That is why everything…

Hi @Vidhya Mohan I would suggest you to use this code instead :) (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(); })…

Hi @Phil Walburn Sorry, but I really don't know, I tried similar thing in the past and it worked. Hard to try fix something that you can't actually touch (but I tried) :) Try to open a ticket about it to Atlassian.

Hi @Phil Walburn Yeah, that's what I meant. What do you mean it didn't work? What the log print? Did you also try 0 (without quotes)?

Hi @Ashutosh Shrivastava Please keep posting to me as under my answer and as new answer (to keep the order of things :) ) Now about your pom.xml files, I'm not sure which one of them, but your plugin should have only 1 pom.xml file, (unless this code is extracted from a jar plugin and the original code is not yours)

Hi @Phil Walburn Try to log the following: {{webhookResponses.body.totalItems}} == 0 And also in different log: {{webhookResponses.body.totalItems}} == "0" Let me know the outcome 

Hi @Vidhya Mohan this will work for you if ($("#issuetype-field").val() == "Task" || $("#issuetype-field").val() == "Bug") $("#qf-field-picker-trigger").remove() But if you are no coding, so you probably don't know where to put it either... 

Hi @[deleted] You can add new action "Set entity property" -> entity type = issue -> property key "label-email-sent" -> property value = true. And in the beginning of your rule, add advanced condition -> first value = {{issue.properties.label-email-sent}} -> does not equal-> true So at first run, the property is false, so…

Ohhh I get it now. No, you can't set such a thing, there is no such built-in option, but it is possible to write a JS to hide it when you want.

Hi @Ashutosh Shrivastava Please share your pom.xml My guess you are no using the right amps version

Hi @Joe Bkk Why are you creating this as 2 different post functions? It might be that the sub-task not showing yet because the process of the workflow transition not finished. I would suggest to it all in one post-function, no reason to make 2, specially if 1 depend the other

Hi @AnupamS Can you please share screenshots? Of the descriptor where the current imports exists, and your classes where you try to add the annotations.

Hi @Phil Walburn Did you try to log {{webhookResponses.body.totalItems}}? Just to check that it prints "0"? If yes, can you show the log? Share more clear screenshots? Thanks

Hi @Vidhya Mohan Can you please share screenshot and elaborate more? What you mean by "configuration field"?

Happy to assist :) Please mark my post as the answer. So this issue will be marked as solved.

use the same thing for the log {{now}}

You have to put a value in the fields. The fields expect a value, if you leave it empty, than the automation will set the fields to be empty, because that's the value you set for them. Just write in your fields (in the automation) and in the log too {{now}} as the first example in the documentations:…

Hi @Susan Hamilton This is the log action i meant Also, in all your screenshots, the date fields are empty, you didn't put any value in the fields...

Hi @Susan Hamilton Thank you for the screenshots, can you please also, go inside the edit field action and take screenshot? i want to see what you put there. Also, add a "log" action, with the same value you try to put in the edit action, so we will see what it prints (also send a screenshot of the log action. Thanks.

Hi @Susan Hamilton Can you please share few screenshots? show what you are trying to do in the automation that does not work for you, what is written in the log? also please make sure and let me know, if the field you are trying to update is "date" or "date & time"?

not for attachments

@Hi @Patrick David I think that locally you can't change it, because "atlas-debug" will always overwrite your settings. But what you are afraid of? you are working locally, if your network secured should be good enough. If you still want to do it, you will have to run a local Jira instance not from your plugin directory.…

Hi @Patrick David I don't understand, you try to debug your plugin locally and failed? Do so, all you need is (as you done) run "atlas-debug". Now from intellij, on the top right click "edit configuration" (near the play button) -> in the window open, click the plus icon on the top left -> drop dow"n appear, select…

Hi @Steve Suranie You can expand/collapse them only manually, but Jira remember the state of each swimlanes, so if you got 8, and you close 6 and keep only 2 open, then next time you go the board and will remember the 2 open and the 6 closed. That's a built in behavior of the boards

Hi @Sascha Ziemann Basically you can't, there is no such option in Jira, and there is no plugin as far as i know that does that. If you know JavaScript you can write something that remove the "add attachment" option for the issue screen or any edit option available in the system, and then make it available in the…

Hi @samuel_arsenault-brassard There is a field "Epic Status" in the system, it's a system field, so maybe you don't have it in your epic screen for some reason, but it exist in the system, so you must look for it and add it to your screen. Once you add it to your screen, you will be able to change the "Epic status" and see…

Hi @Vineela Durbha OK, so simply try to change this line: AJS.$('#customfield_15003').attr("readonly", true); //nfeed field to this: AJS.$('#customfield_15003').attr("disabled", true); //nfeed field