Vikrant Yadav Community Champion

Hi @David Howe :- Working Code for me :- import com.atlassian.jira.component.ComponentAccessor def issueService = ComponentAccessor.issueService def projectManager = ComponentAccessor.projectManager def user = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser() def requestTypeValue = "Submit Form 1362"…

https://community.atlassian.com/t5/Jira-Core-questions/scriptrunner-for-creating-scheduled-issues/qaq-p/103115

Hi @David Howe Try to insert value in custom field using below code :- issueInputParameters.addCustomFieldValue(cf.idAsLong, requestTypeValue)

https://www.youtube.com/watch?v=kdHuvFNE91E

@Kevin Johnson Check out this video it might help you to find location :- https://www.youtube.com/watch?v=IvqFYFOuo-U https://community.developer.atlassian.com/t/building-a-webpanel-in-jira-agile-board-tools/30281

Hi @uday Check the issue type scheme for the project . Note that only standard issue types can be created with no parent using the top Create Button. Others need to be created within a parent issue (that is on the issue view screen using Creating Subtask menu) What kind of issue type is the missed one? Standard or Subtask?…

JIRA now re-indexes sites and projects automatically, so Indexing and Re-indexing have been removed. 

@Evgeniya Slinko Reindexing has been deprecated in Jira Cloud. You do not need to reindex Jira Cloud anymore https://community.atlassian.com/t5/Jira-questions/Can-t-re-index-Jira-Cloud/qaq-p/613607

@serge calderara By default, each active user session lasts for five hours (or 300 minutes) of idle time. This means that a user can log in and leave the computer for up to five hours and their browser session will still remain active. I order to edit follow steps provided by Atlassian in below link :-…

Target start and target end dates in the scope table of a plan in Advanced Roadmaps https://confluence.atlassian.com/advancedroadmapscloud/showing-advanced-roadmaps-custom-fields-in-jira-998651396.html

Hi @Haaris Khan These fields are locked to prevent accidental changes which can subsequently break the operation of JIRA which includes data loss and corruption. Additionally, the locked custom fields are used by JIRA or one of its plugins and modifying it can be harmful to the instance.But you were able to make the field…

@Bruce Fint It seems that in Sub-task field configuration "Original" is set Required and field not avaialble on the create screen. Add field on sub-task issue screen or make field OPtional from sub-task field configuration. thanks, Vikrant Yadav

Hi @DeRuntz Lars RAININ On Cloud instancee you are looking for Server ID. Server ID only avaialble for JIRA Server or Data Center not for CLoud. 

@Anatoliy Strongly Agree. JIRA is perfect tool developement team.

Hi @Gui Ávila For this you have to Put JQL condition. If JQL condition met then In Progress transitionwill be visbile, if condition fails then this transition hides for the user. 

Hi @Tori Krueger you can check workflow post function there might be resolution Set to Resolved.

Hi @Carnegie Technologies Belgrade ScriptRunner provides an option to mimic existing project . 

@Neha Jha Cool, glad to hear that helps. Let me know if you have any follow up concerns. If this answer solved your issue, please click the checkmark to the left of my answer to accept this answer.

@DADSI Haitam Cascading field is best suits for your request. For timesheet i am not sure, which field supported by timesheet reporting or not. 

Are you able to see Setting cog icon on top right corner , if Yes, click that icon and select issue. Then select Issue type Scheme. If not able to see setting, it measn you dont have JIRA Admin permission. https://www.youtube.com/watch?v=H9EXqLz_DA8

@Neha Jha It seems that Issue Type scheme mapped with other projects that's why not visible to you. Check in Issue Type Schemes if you have JIRA Admin permission. Project Admin can't modify Issue Type Scheme.

Cool, glad to hear it helps!

@Steve McEvoy For cascading try this :- customfield in cascadeOption(parentOption,childOption) https://confluence.atlassian.com/jiracoreserver073/advanced-searching-functions-reference-861257222.html#AdvancedSearchingFunctions-cascadeOption%28 

@David Harkins https://library.adaptavist.com/entity/deactivate-users

Hi @David Harkins Check this :- https://docs.adaptavist.com/sfj/automatically-deactivate-inactive-jira-users-11993250.html

@Andrew Sacco CC should be there if it is custom field. 

@Steve McEvoy For Text field JQL search doesn't work like Dropdown field or any other field in which the value is fixed. Search for issues where the description contains particular text. Checkout these link to search issue using text field…

@DADSI Haitam Changing is not possible. It's better to create new cascading field and add in the project. Once field added in the project, then add values to new field for old issues using bulk operation if so many issue or some issue is in then project then do it manually. Once you did the changes in older issue then…

is it a text field or cascading field ? i want to know the field type.

Hi @Steve McEvoy Req Accounts is a custom field ?