Tuncay Senturk _Snapbytes_ Community Champion

Please let me know the result and I may have a further look.

It is really hard to see what the problem is but what I'd do first thing is to add some warning logs in order to trace and understand whether - the change variable's value is true log.warn ("change: $change") - it reaches the block with setCustomFieldValue log.warn ("linkedissue: $linkedissue.key")

I did not find it, I knew it from the past experience. Here is the javadoc for the MutableIssue class and Issue class. You can check their methods there. Could you please accept the answer to mark it as resolved? Thanks

Welcome all! Great to have you here!

Hi @High Performance Welcome to the Community! If you are not on Team Managed project and you are an admin of the project, simply click on Projects (top menu) and select the project in which you want to change the issue type scheme. Then click on Project settings. Then click Issue types on the left menu and you will see…

Hi @padraik I haven't checked every line of the code. setCustomFieldValue is a method of MutableIssue class. Could you please try casting Issue to MutableIssue? In order to do that you have to add an import com.atlassian.jira.issue.MutableIssue then cast the issue object to MutableIssue MutableIssue linkedIssueObj =…

It was my pleasure! Have a wonderful week ahead!

You need to release those issues in order to get rid off them from the board.

Hi @Aisha M Yes, it can be absolutely cleared. If you click on the link "Looking for an older issue?" at the bottom of DONE column, you will see those issues which are hidden from the board and you will have a clear idea why they are still seen in the count (they need to be released or what). I hope that makes sense.

:D fingers crossed!

I am not good at Automation, but it sounds like a brilliant idea. 

If you want to trigger the same email to be sent to users in a user custom field of the issue as well as the stakeholders of the issue (assignee, reporter), I don't think so. On the other hand, you can send emails using script runner, here is a library document on how to send email via script. If you want to send an email…

My pleasure! Please let me know if you have any issues or you need assistance.

Hi @Aisha M As you mentioned, that's doable using Script Runner's Issue Archiver's Job, you can see a youtube video here. However, as @Anzar mentioned, it won't trigger an email to stakeholders which are specified in a user custom field.

Yes, definitely you can do that. I mean, you can use an app to update a custom field value in a transition's post function. However, that would not be only specific to board view, but also issue main view as well as report exporting options (xls, csv).

Hi @Pete P As far as I understand, you need to append some text to the custom field's value on the board view. If that's the case, you can't do that unless you implement your own custom field and code its relevant views (front-end). I could not get the point of how you want to add during a post-function though.

Hi @Naresh It seems that customfield_13800 is used in one of the workflow validators of the transition. Could you please check the transition and make sure there is nothing wrong there?

Hi again! Could you please accept the answer if it was helpful?

Please don't be sorry. It's my pleasure to help. 

Always! Please let me know if you have any questions, mentioning works :D 

project = ABC AND updated >= -30 ORDER BY UPDATED DESC will return the issues which are updated within 30 days in the ABC project descending order

For instance, if you have Enhancer Plugin for Jira, you can use User History Report to filter what users/groups have done within the specified duration.

Hi @Aisha M I am afraid you can't do that for Jira Server. Howeve, in the Jira Cloud there is a built-in function "updatedBy" to do this. There is a ticket (JRASERVER-69208) on Atlassian Jira related to this but I don't think it will be ready soon (or even in the future). You have to use some apps in order to achieve this.

Sure :) 

I think it is best to see your filter and some screenshots if possible :)

Thanks for your kind words @Aisha M and I'm glad that you managed to make it work. What do you mean by the left side got limited? If you include epics, you will be able to see the Epics filter as well as the Versions filter. Other than that you should not see a limited/restricted navigation bar (as far as I know).

As far as I know, you should be able to add sub-task or sub-bug type issues.

@Aisha M ?

Hi @swayamsiddha.choudhury It can be either an intermittent problem or a permission issue. If the user does not have the 'create issue' permission, it can also be the reason. Please use the permission helper to confirm that the user can create issues in the project.

I'm afraid, No. Actually, Jira 5.1 is quite an old version. I know sometimes it is hard to upgrade due to some legacy but I strongly recommend upgrading to the latest version.