Tarun Sapra Community Champion

Here's the problem in your code issueStartDate.updateValue(null, spr, new ModifiedValue(issue.getCustomFieldValue(issueStartDate), startDate), changeHolder); You are passing custom field object "startDate" in the ModifiedValue constructor, it expects an value and not an object. Thus, you should pass "startDateVal " instead…

Since you are using script runner, my suggestion to you is to try out the code in the "Script console" with proper logging so that you can see the log output on the console itself. https://www.adaptavist.com/doco/display/SFJ/Set+logging+to+help+debug+your+scripts

Hello @Nageswara Rao Koppisetti As @Alexey Matveev shared in his response , you can only submit the fields which are part of the transition screen for a particular transition. In your case the transition id is 3 and for this transition you have to check if the transition screen exists and if it doesn't then you should not…

Hello @Aetisam Butt Could you please take a look into the log file because if tomcat is starting and you can see that on the console then you Jira should be available on the port mentioned on the tomcat console.

Looks great!

I ran into an exact same issue as @William Bouzy , it was also due to an browser extension. 

JIRA supports mail handlers out of box. So if you forward email to an email address which is mapped to JIRA project then JIRA will create an issue for you based on the content of the mail and how you can have done the configuration of the mail handler. Read more here…

If you are doing an import directly from Mantis then my suggestion would be to migrate these 3 fields into JIRA's description and 2 other custom fields and then later use a plugin or a script to merge the values of the newly created custom fields into description field. Once the merge is done then you can delete the 2…

Hello @Björn_Schotte Adding to the answer provided by @Andy Heinzer , if you have few spare hours on your hand then you can implement this feature yourself by using script runner plugin. Here's the step by step process * Read the 2 examples here - https://scriptrunner.adaptavist.com/latest/jira/custom-jql-functions.html *…

Thanks @Andy Heinzer for such an nice explanation !

Your welcome @[deleted], please accept/upvote answer so that others are helped as well.

Getting charts based on metrics across sprints or program backlogs which are further divided into project backlogs is not something which is provided out of box in JIRA. You can use reporting plugins like Dataplane or eazyBI for this purpose. I use dataplane currently. Here's some docs about it…

Honestly, I am not sure what could be going wrong as for cloud instance you wouldn't have access to logs as well. Thus, I would suggest to reach out to Atlassian support. https://support.atlassian.com/contact/#/

Some tips here https://confluence.atlassian.com/jirakb/jira-software-kanban-board-does-not-show-all-issues-779158700.html and here https://community.atlassian.com/t5/Jira-Software-questions/How-do-I-make-issues-visible-on-a-Kanban-board/qaq-p/43479

If your JQL filter of the board matches the issues in "ready for 2nd line" then the issues should appear on the board. Can you check in the "column" configuration of the board to make sure you have mapped "Ready for 2nd line" status to an column on the board. Please go through the checklist…

that's strange, which version are you using?

In the "additional issue action" section you have to write this code, there are some sample already for "Set custom field" (click on expand examples) def cf = customFieldManager.getCustomFieldObjects(issue).find {it.name == 'Epic Name'} issue.setCustomFieldValue(cf, 'my value') And place this post-function the last…

Hello @Shawn Danisa What is the error you see in the log files? Is it due to an mandatory field like "Epic name" which you have to set while creating an epic. And if that's the case then you need to set that value in "Additional issue actions"

Hello @mirelm When you right click on the card on your board then you should see the option of "Add flag" on the card, that leads to change of color as well as adding an flag icon on the card itself.

This will be only available initially for JIRA Data center only.

* Project’s data is removed from Jira’s index, which is a collection of text entered into issue fields, used for faster searching. This improves performance by removing data that is stored directly in Jira.

Hello @Fazila Ashraf Yes, that's correct. You can choose not to include JIRA Archived project in the indexing process. This is a much needed performance improvement as old projects will no longer take up index space once they are "Archived" From 7.10 EAP notes ( as actual release is not yet available Changes EAP-02 Project…

import com.atlassian.greenhopper.service.rapid.view.RapidViewService import com.atlassian.greenhopper.service.sprint.Sprint import com.atlassian.greenhopper.web.rapid.chart.HistoricSprintDataFactory import com.atlassian.jira.component.ComponentAccessor import…

You can write a listener for "Start Sprint" event and list the issues or send them in email. Similar Sample here from Script Runner docs

Here's the policy - https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html If you feel my answer has helped you then please accept/upvote the answer. thanks.

Hello @Jonny Klaas Indeed this is an issue, may be you can add a comment on the ticket so that Atlassian might re-open the ticket. Atlassian implements lot of new features in every release but features are picked on various factors and one of those factors is the user votes. And since this particular feature didn't get…

If you are fine with just the "numbers" to appear in chart then you can use the build-in gadget in jira called "two dimensional filter" and choose "Project Name" as Y axis and Sprint as X-axis and that will give you the number of epics based on project name categorization present in each sprint. But if you want a more…

Hello @Jonny Klaas In the JIRA ticket, Anonymous is just used as an example, basically if you have some projects configured for public access then public/anonymous users can see the list of all users in the issue navigator view by clicking on the "Assignee" button pretty much same as in your case. Since you have some…

For cloud instance - https://jira.atlassian.com/browse/JRACLOUD-34165 

It seems to be an open issue which has been declined by Atlassian as won't fix since it didn't gather much votes. https://jira.atlassian.com/browse/JRASERVER-34165