Fabio Racobaldo [Catworkx] Community Champion

Thanks @mferno 

Hi @Dhruv , my suggestion is to apply the following workaround https://confluence.atlassian.com/bamboo/lockout-recovery-process-952624910.html Hope this helps, Fabio

you're welcome @mferno . Please mark my answer as accepted!

Hi @Rabia S_ , in order to do that, as JIRA Admin, you can customize Work Attributes at your convenience. Please take a look to the following guide https://tempo-io.atlassian.net/wiki/spaces/KB/pages/270499978/Dynamic+work+attributes+in+Tempo+Timesheets+for+Server in order to figure out how to do that. Hope this helps,…

Hi @mferno , welcome to the Atlassian community! Epic is an Issue Type so "Open an Epic" means that you should create a ticket with "Epic" as issue type and populate fields based on your own setup. Hope this helps, Fabio

project = X AND ("Severity[Dropdown]" in (S1, S2) OR issuetype!="Bug") ORDER BY priority DESC

At the edit time field mandatory on creation will remain as mandatory. Btw, my behaviour works on both creation and edit.

 @shrikant maheshwari , if you need to setup mandatory fields at creation time please use field configuration. Through the scheme you can define a spefic field configuration for each your issue type. It is a standard approach.

Yes, it should. Btw, if you don't want to see bugs in the backlog why you need to view them at sprint side? Complete this sprint and then edit your board filter. Ciao, Fabio

Hi @[deleted] , please edit your filter board using the following guide https://support.atlassian.com/jira-software-cloud/docs/configure-filters/ Hope this helps, Fabio

you're welcome @Liron Katz 

Hey @Liron Katz , if you need to perform some specific tasks on multiple accounts, you should ask support to Atlassian through https://support.atlassian.com/contact/#/ Export and Import process allows you to move one space from an account to another one!

Hi @Ricardo Gonzalez , you should be able to setup period (weekly) in your gadget. Isn't it? Fabio

Hi @Liron Katz , you should be able to do that simply export your confluence space from your source account and then import it in your the target one. Hope this helps, Fabio

In my local environment it works like a charm. Please verify that your cf id is correct. If you selected all issue types as mapping and put your code in Initializer and Issue Type, it should work.

Hi @Srikanth , did you try to use the following how-to guide https://about.gitlab.com/blog/2021/03/25/integrating-gitlab-com-with-atlassian-jira-cloud/ ? Fabio

you're welcome @[deleted] / @Consulente Atlassian please mark my answer as accepted

Hi @shrikant maheshwari , that is the problem. You behaviour currently works just for bug. If you need to work for all issue types (mandatory field should depends form all issue types) you need to edit mapping so that it works at project level and for all issue types. It should fix your issue. Fabio

Hi @maruthi98 welcome to the Atlassian community! If you're looking for best way to manage tests in JIRA my suggestion is : * https://marketplace.atlassian.com/apps/1213259/zephyr-scale-test-management-for-jira?tab=overview&hosting=cloud *…

Hi @Consulente Atlassian , unfortunately, that configuration could be put in place based on specific group, uer or project role but not based on custom field within your issue. If that behaviour is general, so it affects all your issues within your project you can provide edit permission to that group custom field. It…

Hi @shrikant maheshwari , if you need to make field mandatory based on issue type, the best pratice says to use Field Configuration Scheme based on issue type. Btw, your code should work, I jest tested it in my local environment. Please could you share the mapping for your behaviour?

You're welcome @petrvokoun . Please accept my answer so that this thread can be considered closed.

Please read the following guide https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/ You should use Updare Issue Field post function selecting your desired assignee. Ciao, Fabio

Hi @petrvokoun , here an official statement provided by Atlassian https://confluence.atlassian.com/doc/confluence-security-advisory-2021-08-25-1077906215.html If you can't upgrade your current Confluence , you can mitigate that issue through the workaround provided by Atlassian in that article. Hope this helps, Fabio

Hi @Prashant , in my opinion, you could just use a post function that change assignee value each time that transition happens. Fabio

Hi @shrikant maheshwari , Initializer works when you open the edit/create screen. If you want that your code works when change a specific field you need to add the same script also for that field. In your scenario, you need to put the same code at Issue Type field level It should fix you issue. Ciao, Fabio

Hi @Stefannie Tan , in order to do that, please update your Scrum Board filter so that also ticket from different project will be retrieved. Please read the following guide https://support.atlassian.com/jira-software-cloud/docs/configure-filters/ Hope this helps, Fabio

Hi @Devendar Gangapuram , in order to have build information within a JIRA issue, you need to have a key of jira issue at build level. Read here for further information : Linking Builds to Issues Jenkins builds are linked to Jira issues if a key of an existing Jira issue can be found in the job and build data that was…

Hi @Badana Shanmukha Teja , at portal side, you can't set a default value for a field (https://jira.atlassian.com/browse/JSDSERVER-4133) The only way to do that is a behaviour provided by ScriptRunner app. Sorry for that. Ciao, Fabio

Hi @aas , I don't figure out the reason. Listener works after creation because it start after that create event is fired as last post function in creation. Based on that, when listener works, issue should be created and in correct status.