Thorsten Letschert [Decadis AG] Community Champion

Hi @Pat , the approval functionality provided by JSD is probably the correct spot already. If you want to pre-set the list of approvers, you can do so by heading to 'Edit request type', clicking 'Hide' on the 'Approvers' field and selecting those 5 users. In the screenshot you've added you basically just control the number…

Hi @Guhan , I know it's been a while, but in case you didn't already come across, the latest releases of JWT for Jira Cloud, tons of features have been shipped in the meantime including support for updating the sprint field. That said: have you been successful in implementing your use case? Cheers Thorsten

Hi @Donata , the correct answer might depend on the question, whether those issues should 'only be hidden in the board' (but still accessible in general) or 'be hidden in general', If the issues could remain visible in general, configuring a slightly adjusted board like suggested by @Mohamed Benziane might do the trick.…

Hi @hannah.brooks , while there is still no out-of-the-box feature to do so, you might want to have a look at the workflow apps available on the Atlassian Marketplace: https://marketplace.atlassian.com/search?category=Workflow Jira Workflow Toolbox being one of those can manipulate the labels field via its Update issue…

Hi @Hendrik Hess , is the user you're about to mention * a customer/external user without a Jira license or * an internal user with a Jira license? In general, Jira only offers users who are actually permitted to see the current issue within the comment field. That said, the user has to have the Browse projects permission…

You're welcome. However, since you have Script Runner at hand, this should do the trick then!

Hi @Ingo Mohr , the 'Update Issue Custom Field' post function actually is only available for Jira Cloud. When dealing with Jira Server or Data Center, you'll need an additional workflow app - see https://marketplace.atlassian.com/search?category=Workflow Cheers Thorsten

Hi @Ilakiya Srinivasan , while I'm not aware of this kind of more advanced' workflow functionality being available in Jira Server and Data Center out of the box, you should head over to one of the workflow apps available on the Atlassian Marketplace - see https://marketplace.atlassian.com/categories/workflow What you're…

Hi @Matthias Rohde , I guess you'll just have to test against Jira 8.11 yourself. Due to some larger changes in Jira 8.12 I'd assume that there will be problems then at the latest. Regarding the actual app usage within the workflows present, I'd recommend running a workflow report provided by Admin Toolbox for Jira…

Hi @Alan Bruce , a sub-task always inherits the issue security level from its parent. There's no way to change it independently - see https://jira.atlassian.com/browse/JRASERVER-5869 Cheers Thorsten

Hi @Elena Kotsinova , when you want to make a field required in general for a specific issue type, I'd go for updating the corresponding field configuration and make it required there - see https://confluence.atlassian.com/adminjiraserver0810/specifying-field-behavior-1014673967.html Cheers Thorsten

While I'm with Nic here in general, a final judgement can only be made knowing which post function you're referring to in particular here (as well as Jira default vs. app?).

Hi @Heather Dubin , Jira Service Desk approvals rely on the following configuration made within the workflow: That said, once you enter an approval status, the users defined by the 'Get approvers from' configuration (here: users selected in the Approvers field) will receive an email to approve the issue. Per default, only…

Hi @Piyush saxena , the easiest way is probably to * remove the custom field from the default edit screen * add a global reflexive transition (from any status to itself) * add the custom field to the transition screen * add a condition to this transition so that it can only be executed by the users or group of interest…

Hi @Kishore , so that the public can also participate in the solution we worked out via our support, here again briefly summarized: The goal was to distinguish between users with a 'default' username and users where the username is an email address, e.g. demo.user vs. demo.user@example.com This was achieved with a boolean…

Hi @dhruv.chheda , I guess you're referring to the board instead of the backlog and that probably the newly created statuses aren't mapped to any board column - see https://support.atlassian.com/jira-software-cloud/docs/configure-columns/ Cheers Thorsten

Hi Tim, please update the Who can customers share requests with section as mentioned above. Cheers Thorsten 

Hi @Tim Peters , could you please check for the Customer permissions settings, since the second option has to be set to Any customer or organization in order to make those user pickers work. Cheers Thorsten

Hi @Bo Glenn , There should be a 'Satisfaction settings' menu entry in your Project settings if you're using a classic project. For next-gen, it's 'Customer satisfaction'. Cheers Thorsten

Hi @Radhika Vijji _Innovalog_ , Thanks for the addition - of course groovy can be incorporated as well. However, I assumed that with the 'Easily configure workflows, WITHOUT CODE' claim the target audience is rather the UI people instead of the scripting ones. Just learned that you want to serve both, by definition. Cheers…

Hi @Peter Borzenkov , I'm not aware of any free apps and obviously biased, since I'm part of the team behind Jira Workflow Toolbox. That said, I'd guarantee that this app is capable of all the things mentioned in your initial post (and much more). However, the same probably applies for the other no-coding solutions like…

Hi @Peter Borzenkov , since those 'more advanced' workflow elements aren't available in Jira Server and Data Center out of the box, you'll have to head over to one of the workflow apps available on the Atlassian Marketplace - see https://marketplace.atlassian.com/categories/workflow Cheers Thorsten

Hi @[deleted] , all the statuses used can be re-ordered at * yourCloudURL.atlassian.net/secure/admin/ViewStatuses.jspa (on Jira Cloud) * yourBaseURL/admin/ViewStatuses.jspa (on Jira Server/Data Center) This order is taken into account when sorting or grouping by statuses. Cheers Thorsten

Hi @Juliane_O , since you're mentioning the sub-task creation via post function, you're probably using a worklfow app (issue creation via post function isn't possible in Jira out of the box). Could you please tell us which one you're using? Cheers Thorsten

Hi @Fernando Passos , with regard to Jira Workflow Toolbox, an automation rule as easy as should do the trick. * Create a new automation rule * Choose an Issue event - Issue commented trigger (or Issue updated if that's what you're after) * add a Transition issue action with the transition of interest If you need more…

Hi @Pete Piro , all the statuses used in classic projects can be re-ordered at yourURL.atlassian.net/secure/admin/ViewStatuses.jspa This order is taken into account when sorting or grouping by statuses. Cheers Thorsten

Hey @Robert P , Thanks for the feedback - you're always welcome. For future reference using the ID should work as follows: getFieldById("customfield_12345") Cheers Thorsten 

Hi @Robert P , have you been successful?

Hi @Robert P , thanks to my attentive colleague @Max Foerster - K15t who takes his role as a community champion very seriously, I've been looking for a behaviour related solution once again and came up with the following: import com.atlassian.jira.bc.issue.search.SearchService import…

Hi @Robert P , unfortunately I can't help you with a custom script. However, if evaluating an additional app is applicable for you, a solution including Jira Workflow Toolbox is as easy as: * Adding a boolean validator * Use an expression as follows count(issuesFromJQL("key = " + %{00015} + " AND 'your_SLA_name' =…