Thorsten Letschert [Decadis AG] Community Champion

Hi @Николай , actually there seems to be a known issue with regard to Service Desk related visibility options that is about to be fixed with the next version 2.6.2 - probably to be released this week. So please watch for updates. Cheers Thorsten

Hi @Josh_Castiglioni , what you're trying to achieve should be absolutely possible given the built-in functionality of Jira. Please be aware of the fact, that boards are just some kind of view on a certain collection of issues. That said, boards could include issues from different projects and issues could be shown on…

Hi @Pooja Patel , if you're running on Jira Server and using a third-party app is applicable for you, you might want to have a look at Jira Workflow Toolbox. Examples regarding the auto-assignment to project-related users can be found here. Cheers Thorsten

Hi @Николай , are you referring to Jira Core/Software or Jira Service Desk visibility restrictions? While this feature won't be available out of the box, you'd be able to so with the help of Jira Workflow Toolbox since it provides lots of possibilities to customize your workflows with regard to conditions, validators and…

Hi @Alexandru Mihaianu , referring to Jira Workflow Toolbox, a potential Boolean Validator place within th Create transition of the issue types you're creating could read: %{00014} in ["Bug","Task"] IMPLIES %{10100} = null Short explanation: If the issue type equals Bug or Task (first part of the expression), the Epic Link…

Hi @Javier Perez , with regard to workflow elements like conditions, validators or post functions you might want to have a look at Admin Toolbox for Jira. Its built-in workflow report provides the exact analysis you're looking for. All the relevant functionality is obviously available within the usual 30 days trial. Cheers…

Hi @Floyd Goodell , First of all there are no silly questions. Since we're running this post function within the parent issue, we'll have to use %{00015} instead - my bad. A valid expression might look like this: getMatchingValue(^, [1,2], ["Info Sec Review", "Accessibility Review"]) + " (" + %{00015} + ")" With this…

Hi @Floyd Goodell , Actually you can do this within Jira Workflow Toolbox very easily since we're providing direct access to so called Virtual Fields, e.g. * Parent's issue key - %{00041} * Parent's summary - %{00029} You can use those field codes when creating your subtasks to include, e.g. append, those to your subtasks'…

Hi @Raj Kumar , While Basic Mode has some built-in logic and narrows down the options provided, e.g. if you choose a project only the statuses from the workflows used by this project are displayed, Advanced Mode won't do such filtering. To get rid of those statuses there, you'd have to delete them globally (only if you're…

Hi @Tamas Varga, Thanks for the feedback. If all the permissions are correct and the statuses are mapped, it sounds indeed like a strange behaviour. You've mentioned migrating - have you already tried to re-create this board? I'm hinting towards the question of whether boards aren't working at all or only migrated boards…

Hi @Tamas Varga , If the workflow seems to be finde, please check the board settings for the correct status mapping. Head over to Board > Configure > Columns. In order to drag and drop your cards, the statuses have to be mapped with the corresponding columns. Cheers Thorsten

Hi @Kylie Manning, hi @Petter Gonçalves, given Kylies last comment, she stated to have installed Epic Sum Up - which is in fact another app. :) Right before, we were talking about sumUp for Jira. Unfortunately I can't say anything on whether Epic Sum Up is capable doing what is requested. So @Kylie Manning please install…

Hi @Kylie Manning I hope you don't mind me stepping in. You can in fact group your results by assignee: Just click Edit to access the gadget configuration and choose Assignee in the Group Field Y section. Cheers Thorsten

Hi @Semi Ajibola , A spontaneous assumption: is it possible that email notifications related to the events you're describing are somehow backfiring into the mailbox of your service desk project? Another try might involve checking for the usage of automation apps, e.g. Automation for Jira. Cheers Thorsten

Hi @Heather Hargreaves , Everything's fine. Just wanted to make sure we're on the same page. Basically, two prerequisites should be full-filled: Your user needs the global permission Browse users (https://confluence.atlassian.com/adminjiraserver080/managing-global-permissions-967897260.html) Users you'd like to mention…

Hi @Heather Hargreaves , Since this question has been added to Jira Service Desk: are you referring to the Jira issue view or the customer portal? In the latter case, @-mentioning is unfortunately not possible. In the first case, I'd check for the Browse users global permission. Cheers Thorsten

Hi @Helen Rodgers , as Nic already mentioned you'll need an additional app to do so - either for scripting, e.g. ScriptRunner or one of the workflow enhancement apps (see https://marketplace.atlassian.com/categories/workflow as a good starting point). An example related to one of those, referring to Jira Workflow Toolbox:…

Hi @Prasad Andrews , Thanks for your feedback. I'm glad that I could help you. Could you please mark the answer as correct then? Cheers Thorsten

Hi @Matúš Klaudíny , A couple of thoughts: you could use the approach mentioned by @Dave Bosman _Inetum_ with a little adjustment: * Use the SLA to transition the issue from (let's say) "Open" to "Ready for Escalatation" and hide this status change from the user via the customer visible status ("Ready for Escalation"…

Hi @Prasad Andrews, if those two issues (and only those two issues) are linked to your candidate issue, a configuration like shown here should be enough: If there are potentially more linked issues, you might want to add some filters to ensure that only the relevant issues are updated. Cheers Thorsten

Hi @Prasad Andrews , you might want to add an Update issue fields post function to your 'candidate offer approves' transition in order to distribute your Due Date to the related issues. Is there a relationship between your issues candidate, background check and drug screen, e.g. issue links? If so, use this relationship in…

Hi @Cloud9_GE , Since this functionality isn't available in Jira Server out-of-the box, you'll need a 3rd party app, e.g. * Jira Workflow Toolbox (https://marketplace.atlassian.com/apps/29496/jira-workflow-toolbox) * Jira Misc Workflow Extensions (https://marketplace.atlassian.com/apps/292/jira-misc-workflow-extensions) *…

Hi @Yoganand S, are you on Jira Server or on Jira Cloud? Cheers, Thorsten

Hi @Marc Jason Mutuc, so you're trying to export your issue navigator result to *.CSV and receive your durations in pretty short format, e.g. 1d 1h 34m, instead of 920611160000000 ms? If this value is for reporting purposes mainly, I'd rather suggest using a Calculated Text Field with the following expression:…

Hi @Marc Jason Mutuc, regarding your status changes, the timesOfTransition might help solving your request (see the comprehensive list here: https://apps.decadis.net/display/JWT/Expression+Parser). An example: first(timesOfTransition("", "In Progress")) This expression returns the timestamp when the issue was first…

Hi @MEDITECH ADMIN TEAM, please try the following expression: (%{15703} != null AND %{13608} != null) ? (toNumber(%{15703})*toNumber(%{13608})) : 0 It returns your requested calculation if both fields are set and 0 otherwise. Please let me know if that solves your problem. Cheers, Thorsten

Hi @MEDITECH ADMIN TEAM, have you tried the expression without the quotation marks? If you're experimenting with parser expressions and run JWT 2.4.0 or newer, I'd clearly recommend testing your expressions on the newly added Parser Test Page (see the documentation…

Hey @Thomas Schlegel, please allow me one little remark for the sake of completeness: it's of course possible to transition linked issues with Jira Workflow Toolbox as well - with a highly configurable issue selection (see https://apps.decadis.net/display/JWT/Transition+issues). Nevertheless, I voted for the answer. @A…

Fixed a small typo. Obviously it should read != instead of =.

Hi @Floyd Goodell, this is exactly what the function (IMPLIES) is for: if and only if your specific team is selected, then the other field is enforced to be set. So everything should work fine. If you're experimenting with parser expressions and run JWT 2.4.0 or newer, I'd clearly recommend testing your expressions on the…