Tuncay Senturk _Snapbytes_ Community Champion

Hi @nd10 You can change the filter query for the board (Configure Board > General > Filter) not to see them in the backlogs section.

Devil is in the details, Please find atlassian-jira.log file and try to find the very first exception stack trace while Jira was trying to run. There should be many stack traces since almost all apps fail while starting.

Hi @mefthymiou Welcome to community. There is a permission "View Development Tools". You should be granted for this permission within the related project.

Hi @Daniel Davies Unfortunately, there is no way to achieve this out of the box. Actually it is also not considered to be done. Here is the related issue for this, you can vote/watch it. https://jira.atlassian.com/browse/JRASERVER-2734 So, you should use apps as described in the issue: - Enhancer Plugin for Jira - CCC Last…

My bad, I think this should work <span>issue.setCustomFieldValue(dateACF, </span>new Date(dateB.getTime()))

I'm glad that it helped. Thanks for your kind words.

It should look like below: import ... def log = Logger.getLogger("com.nolddor") log.setLevel(Level.DEBUG) def event = event as IssueLinkCreatedEvent def issueLink = event.issueLink def sourceIssue = issueLink.sourceObject def destinationIssue = issueLink.destinationObject

Hi, Most probably it is compile time error, you can add below line just after the import statements. def event = event as IssueLinkCreatedEvent

Hi @Francisco Gomez Balastegui What error(s) are you getting in the console or in atlassian-jira.log file?

Or in your code you should convert GregorianCalendar to date issue.setCustomFieldValue(dateACF,dateB.toInstant()) 

Hi @Tom You can simply add 365 days as below def dateB = dateAValue.plus(365)

Sorry, those security logs do not give a clue. If you change default log level to DEBUG, it might be helpful, but I'm not sure though.

Hi again, Is it possible that you use same code for different event types? For your first run you got below error: No such property: issue for class: com.atlassian.jira.event.issue.link.IssueLinkCreatedEvent As I mentioned for IssueLinkCreatedEvent you can get source and destination issues with the code I provided. In the…

Hi again, You should remove def issue = event.issue as Issue

Hi @kalim7 Do you want to achieve this by an app from Marketplace or by your own plugin? I mean there are several methods to implement such a post function.

Hi @[deleted] Have you checked the atlassian-jira.log file? I reckon there would be something meaningful there which will give us clue to fix the problem.

Hi @vgross You should be more clear. What do you mean by Defects numbers report?

Hi @BarL IssueLinkCreatedEvent does not have Issue access directly as seen in the API here. Because there are two issues that are linked. You can get event.issueLink and then get Source and Destination issues as below def issueLink = event.issueLink def sourceIssue = issueLink.sourceObject def destinationIssue =…

I'm glad that you found the devil ;)

You can add input fields (text, radio, check, select) to this vm file and access them in your java file. Also you can get pre-defined values in your vm file by $action.field And yes, you have to add getter/setter

Do you have editDemoHandlerDetails.vm in the right folder? And does your EditDemoHandlerDetailsWebAction class contain those fields' (in vm file) getter/setter?

Hi @Kim Hood Welcome to the community. error.500 is so common error and you can't understand what's behind without having a look at server log files. Please find the related stack trace in the log file and try to understand what's the actual problem. If it is hard to understand, you can attach here so that we can have a…

Hello, Have you tried to add vm resource file in <actions> tag as described in the tutorial? You need to add getter and setter methods in EditDemoHandlerDetailsWebAction class (assuming it is your action class) per each inputs in your vm file.

How about this one? // add these to the import statements import com.atlassian.jira.issue.util.DefaultIssueChangeHolder import com.atlassian.jira.issue.ModifiedValue def oldValue = issue.getCustomFieldValue(cf) def newValue = optionsManager.getOptions(fieldConfig).getOptionForValue("Yes", null) def changeHolder = new…

Or you can try this one import com.atlassian.jira.issue.util.DefaultIssueChangeHolder import com.atlassian.jira.issue.ModifiedValue import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.user.ApplicationUser def customFieldManager = ComponentAccessor.getCustomFieldManager() def userCf =…

Hi @Bogdan Gorka Could you please try with adding below line after setCustomFieldValue? def issueManager = ComponentAccessor.getIssueManager() issueManager.updateIssue(user, issue, EventDispatchOption.DO_NOT_DISPATCH, false) And please give us more details, are you getting an error?

Great :)

Hi @Jordan Berry Those properties that can be accessed via issue.* are the issue fields. However comment is not an issue field. As you know, there might be multiple comments and you can't access the latest one without code or a third party app which gives you the last comment as a custom field. You can write your own Last…

Hi @sankar sankar If this answer helped you, or you believe it is the right one please accept it so that other community users would benefit. And for the clarification, please do not add other unrelated contents' links, I'll have a look though.

If you want to hide issues from Kanban board after closing them, you need to release them. The link Release can be seen on top of rightmost (Closed, Done) column. Actually, the idea in Releasing a version (Kanban) is the fix version because by default Kanban boards have below JQL in Kanban board sub-filter setting in…