Fazila Ashraf Community Champion

Hi @Will Willis After Jira re-index is done, empty the cube (in Analyze tab) and then run an import on an empty cube. Emptying the cube forces full data re-import. https://docs.eazybi.com/eazybijira/data-import/jira-issues-import#JiraIssuesImport-Re-importallissues

Hi @Roberta You could use groovy script to do this. May be https://stackoverflow.com/questions/4363952/is-there-any-java-class-to-get-date-from-cron-expression would help

Hi @Natalie Reppa Check whether the user accounts has browse permission to the project where the EPIC is created. And also whether there are any security schemes applied on that project.

Hi @sunny gorasia Refer to https://atlassiancommunity.slack.com/apps/ADZHDM3L1-jira-server

Hi @Suhas Pawar Severity is not a built in field in JIRA. You can ask your administrator to create this as a custom field if required.

This works - https://confluence.atlassian.com/jirakb/set-remaining-estimate-to-0-on-post-function-304579031.html

Hi @Mark King Many possibilities. * Check whether the user is part of jira-users group or the jira-core application access group set up in your instance. * Check whether the user has a captcha lock on the account * Check whether the user uses correct credentials.

Hi @Vadim Lazuko The users with schedule and edit permission will be able to reorder tasks in sprint. For the ones that shuffles happened, check on the issue history who changed the ranking of the issue. For the ones that doesnt get reordered when tried, check on these 2 permissions 

Hi @Mo Omar The edit permission in the project's permission scheme gives this ability to the user. But he would be also able to create new labels in the system. 

Hi @David Abowitt Instead of hasLinkType , use hasLinks -> https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_haslinks That takes the inward/outward linkname (Is RCA Remediation) as parameter. 

Hi @Ricky M There is a way to hide the 'Configure fields' option though. Refer to https://confluence.atlassian.com/jirakb/how-to-hide-the-configure-fields-button-on-the-create-issue-screen-608731486.html

Hi @Samreen Farooq You can get this data from the Backlog mode.. Click on the highlighted three dots. 

Hi @Dave Girgenti Could you check whether the description field is in the screen when you click on the 'Edit' of the issue? If it is not there, please have your jira admin add it.

Hi @Joachim Schittenhelm If the workflow is not shared, you can make this changes to the workflow and it reflects only in the project. Also, You could branch out the workflow if it is shared and make those changes.

Hi @Joachim Schittenhelm That order is unfortunately not controlled by the column but by the global status order. If you are the jira admin, you could update the workflow properties on the status with the 'opsbar-sequence' values…

Hi @Archana Refer to https://www.atlassian.com/licensing/jira-software You can get quote in https://www.atlassian.com/purchase/?purchaseMode=quote

Thank you for updating :)

@joe cromie , May be you will have to enable Parallel sprints? https://confluence.atlassian.com/jirasoftwareserver0713/using-parallel-sprints-965542557.html 

Hi @Radha Kandimuthu Something like this in your JMEW add-on postfunction condition

Hi @Eitan yomtovian That is the expected behaviour. Only the fields that are in the screen you are associating for view operations will be visible when the ticket is viewed. Create a new screen with all the fields of the project in it. And set that as the view operation screen

Hi @Eitan yomtovian Refer to https://confluence.atlassian.com/adminjiraserver/associating-a-screen-with-an-issue-operation-938847289.html for details about the screen scheme and the 'view issue' screen association. There would be a screen associated to the view operations of the ticket. You will have to find it and add…

Hi @[deleted] Can you try to create the epic in jira 'create issue' screen to see the required fields?

Hi @Eitan yomtovian For the first problem, you will have to add those 2 new fields to the view screen of the issue type in the screen scheme. For the second problem, making a field mandatory in field configuration scheme means it is mandatory in all the screens including create. For this use case you can use validators…

Hi @Shannon Masterson Look at the permission scheme of the other software projects and see who can 'create issues'. As the client cannot see the projects from the side menu, he might not have the 'Browse issues' permission to the other projects. Check if you could set the create issues permissions of the other projects…

Hi @Radha Kandimuthu We did something similar. What we did was, we put a condition to auto create those tasks only when a custom field value is 0 and in the next post function, we update the cf value to 1. So again when the transition happens, the auto creation will not happen as the cf value is not 0.

Hi @G Krithica JIRA Data center do not include auto scaling feature. JIRA DC on AWS will help on scheduling for an additional node. But it takes some time to bring up the node and doesnt really work like auto-scale based on load. But when you know when a country's user base is going to login and add more load, you can…

Hi @Liat Kimhi Refer to https://confluence.atlassian.com/adminjiraserver072/working-with-workflows-828787890.html and look at the below limitations of editing an active flow So for this workflow where you have to have add a first new outgoing transition, make a copy of the workflow and make those changes and then replace…

Hi @Joe M There is a SWAP sprint REST API https://docs.atlassian.com/jira-software/REST/7.3.1/#agile/1.0/sprint-swapSprint Will that help you?

Hi @Alexander Ivanov You can use Validators for this use case. https://confluence.atlassian.com/adminjiraserver0713/advanced-workflow-configuration-964983727.html#Advancedworkflowconfiguration-validators Forgot to mention that the field required validator comes from the JSU plugin…

Hmm.. If it is all good in the workflow, please try running the integrity checker. I recently faced a situation similar to this and running integrity checker fixed it