Vikrant Yadav Community Champion

You’re Welcome 😇 Have a great weekend 

Hi @Dan Hansen Welcome to Atlassian Community! It seems that you are trying to issue data, collecting custom field value of an existing issue. Above code is for getting custom field context, one custom field have multiple context, jira admin create separate context for each project in which a custom field is used. This…

Hi @Alex Kindly use following script for adding multiple users as watcher, update usernames as per your requirement :- Kindly move scripted post function after "Creates the issue originally." post function, if you are applying script on create issue transition. import com.atlassian.jira.component.ComponentAccessor def…

You’re Welcome 😊

Great 👍.. glad to hear I am able to help you out 😊

If you are using Company Managed project, then only you see Screens under Issue section, if screen is mapped with any other jira project then you can't add new fields on screen. For Adding Epic Status field on screen, kindly ask your JIRA Admin. Thanks V.Y

Thanks for the screenshot. You are using Team managed project, i shared steps for Company managed project. In Company Managed project, Epic Status field is available. For Team Managed project, Epic Status must be Done and Resolution also set to Done.Then it automatically removed from Backlog. Thanks V.Y

Hi @Warrick Bayman Go to Project Settings >> under Issues section go to Screens > Open Epic Issue type Screen and check Epic Status field is avaiable on screen or not ? Thanks

Hi @Warrick Bayman Kindly check Epic Status field is set as "Done", When Epic Status field is Done Epic automatically removed from Backlog or you can manually Mark as Done to remove Epic from Backlog. Hope it works for you. Similar post…

Hi @Asta Adamonyte You can append Summary + Custom field value using Script Runner plugin ( Scripted post function) or you can JSU suite plugin postfunction Copy Value From Other Field (JSU) or you can use project automation plugin(availalble in JIRA Cloud and JIRA DC). Other plugin are also available in Marketplace. But…

Hi @[deleted] Welcome to Atlassian Community! Yes, you can create issue from MS Teams. For this first you need to integrate your JIRA instance with MS Teams. By installing JIRA Cloud app in MS Teams. Kindly follow the steps perfromed in below video for integrating jira with Teams :-…

Hi @Amy Vassallo Renderers affect the rendering (view) of a field's value. This means that you can migrate to a different renderer without affecting your issue data; only the view will be changed. It also means that if you do not like the way your issues look using the new renderer, you can simply switch back with no…

Hi @David Vanzandt Kindly check the workflow, check transitions going to Done status and check post function Resolution is set to "Resolved" or "Done" or something else is availalble or not for Done transition ? It seems that Resolution post function is not avaialble in workflow that's why not updating the Resolution field…

Thanks @Nic Brough -Adaptavist- @Fabio Racobaldo _Catworkx_ , let me give it a try. Will message you if i face any issue. 

Hi @Nic Brough -Adaptavist- who will provide internal URL, do i need to check with network team for internal URL or ask them to create a new url for JIRA ? Once Internal URL is provided, i need to setup Reverse proxy in JIRA (server.xml file) following steps in links shared by @Fabio Racobaldo _Catworkx_ and ask network…

Hi @Nic Brough -Adaptavist- I don't own this domain. I only want to change the name URL, it's accessible on Intranet only. Do i need to own the domain first ? Thanks

Hi @RNV Jira1 Welcome to Atlassian Community! Are these (Field 1, Field 2, Field 3 and Field 4) number fields or single select list fields? Thanks V.Y 

@Ram Kumar Aravindakshan _Adaptavist_ Kindly suggest. Following script is not working when cleaning unused screens using script console :- Getting error :- groovy.lang.GroovyRuntimeException: Could not find matching constructor for:…

You’re Welcome 😉 

Hi @Trent Becker Welcome to Atlassian Community! Kindly check in diagram mode, there might be two same transitions. Kindly remove "All" transition, keep other transition to remove (2)

Hi @Suresh Kumar Welcome to Atlassian Community! Script you are using is for JIRA Server and JIRA Data Center. It doesn't work on JIRA Cloud. For JIRA Cloud, I am not sure how bulk deletion work in JIRA Cloud but Atlassian is working on, you can vote this issue :- https://jira.atlassian.com/browse/JRACLOUD-71733 Some…

Try to add Custom scripted post function of adding comment having linked issue key and bug summary :- Kindly check link type of Bug in issue linking, if it's Outward change getInwardLinks to getOutWardLinks and change commentBody as per your requirement. import com.atlassian.jira.issue.link.IssueLink import…

@CHINNAMUTHEVISAI.SATYANARAYANASHARMA It's not possible to add Issue key in a comment using JSU automation suite. Kindly use Scriptrunner post function to add custom comment on an issue. Add a comment to this issue [ScriptRunner] OR Adds a comment to linked issues when this issue is transitioned [ScriptRunner] Thanks V.Y

Hi @Heidi Fry Welcome to Atlassian Community! It's very easy to setup csv file for epic/story, kindly setup file similar to below table :- Map Epic Name with Epic Name field, Summary with Summary and Epic Link with Epic Link in csv import. Issue TypeEpic NameSummary Epic LinkEpic New Release 15.5iOS new version Story New…

Yes...Bug ..

I have tested on my side using Parent/Child Link type. it's working fine. Comment is adding on Parent issue (Story). It seems that you are doing something worng in issue lik relation in post function. Please make sure, Add comment post function must be after create issue post function. Thanks V.Y

Move post function after child issue creation post function. Bug is a link type, right ? Thanks

Select link type bug instead of Related to . 

May I know which link type are you using when creating child bug issue ?

Hi @CHINNAMUTHEVISAI.SATYANARAYANASHARMA Yes, post function should be on parent issue. It seems that you selected the wrong issue link relation. Check issue link relation, select correct link type. Thanks