Tarun Sapra Community Champion

Why don't you just use a built-in pie chart??? jql = Requirements ID is not empty -- generate ap ie chart and the issues which don't have it will have the value irrelevant.

yes after reindexing also the project list didn't appear. it's a test instance thus i am reverting back to the older stable state and will try the groovy script plugin instead of directly manipulating the db

yes after reindexing also the project list didn't appear. it's a test instance thus i am reverting back to the older stable state and will try the groovy script plugin instead of directly manipulating the db

yes i know about jira.editable wrokflow status property, but the change was reuiqred across multiple projects thus I didn't want to make changes in diff. workflows or use global transitions that loop back on the same status just for the sake of updating workflow but I guess as the KB article suggests it's one of the few…

Using bulk edit isn't the best possible approach as the final workflow state is non-editable, ofcourse we can make it editable but the thing is that this change needs to be implementated across multiple projects. Thus updating each and every workflow isn't a great idea.

Hi Peter, Yes I know of JellyScripts and Escalation services of script runner plugin, the point I was trying to make was that If the approver wants to see the subtasks before approving the parent and the moment parent is approved the sub-tasks are also approved. Yes subtasks can be created if they aren't present at the…

Hi Peter, I agree with you, but what if the approval depends on the number of subtasks currently the parent has? Regards Tarun

Done - issueFunction in hasLinkType("Epic-Story Link") and issuetype = Epic and status = "R&D Backlog" Too bad you can't use the best JIRA plugin - script runner just becasue your using ondemand!

Done - issueFunction in hasLinkType("Epic-Story Link") and issuetype = Epic and status = "R&D Backlog" Too bad you can't use the best JIRA plugin - script runner just becasue your using ondemand!

Hi Maarten, Your answer will give subtasks but the question is about linkedIssues not subtasks.

"Epic Link" is not EMPTY and Status = " XYZ"

I am afraid it's not possible without writing some custom javascript hacks. See here - https://answers.atlassian.com/questions/161414

Most of the "create sub-task" plugins including the script runner work only on hosted JIRA and not on the Cloud instance.

Please see here your answer - https://answers.atlassian.com/questions/13406965

I don't think you can - https://confluence.atlassian.com/display/AGILE/Using+JIRA+Agile+Simplified+Workflow "Displays no screens on any transitions – all transitions will happen instantly"

Thanks @Adam Wride for the clarification

Maybe then you should raise a ticket in Atlassian support.

Hello @Gabor Peter Make sure the username which is committing the code is the same in JIRA along with the same email address, if that's not the case then JIRA git connector user might be getting used.

I have implemented this feature using a groovy script on the create issue validation phase.

my bad, yes i meant validators on create transition. I can use groovy script to achieve this functoinality using the scripting plugin.

Hi Eddie, Yes I agree with you regarding - Major and minor have nothing to do with potential database impacts But generally what I observe in Jira versions is what share with others, and upgrading/migrating within the same major jira version is hardly any trouble.

Just make sure you thoroughly test all the plugins on the updated version on a test machine before making the actual move.

Hi Nick, The upgrade process should be semmless because you are migrating within the same major JIRA version Is it OK to to do the database export as listed in the online documentation from one version and then import it in to the new version? Yes, i think the above approach should be fine. Only thing you need to be…

select * from customfieldvalue where issue=(select id from jiraissue where pkey='JRA-5448') I ran a query similar to the above one, in both prod and test, In prod it returns me the result but in test it doesn't return any result! does the data get deleted while IssueType Scheme migration?

HI @Heinz Wittig , were you able to solve the issue? can you share your java code in a gist file over github?

no need to authenticationContext, Component accessor can be imported easily

it's part of admin section of the script runner plugin, i guess you have script runner installed, using the console it becomes easier to troubleshoot issues in groovy https://answers.atlassian.com/questions/277703

If it was a permission problem then getIssue() would have been null resulting in null pointer exception, from the docs - " the issue will be null if the issue does not exist or the user does not have permission. " But you don't get NPE instead you are able to call getFixVersions() method on the mutableIssue, did you try…

You can use validation phase of workflow create transition and put in a groovy script using script runner plugin which does the check of the "If EPIC LINK = "LIST 1 EPIC" and Issue Type = "DOC" it will work." otherwise it returns false in the validation and thus showing an error message. 

It's not possible as of now.