Thorsten Letschert [Decadis AG] Community Champion

Hey @Jadranka Perc , A simple 'Field required' validator might not be sufficient for your use case. You should look for a workflow app capable of interpreting Jira expressions (see https://marketplace.atlassian.com/search?category=Workflow&product=jira) and an expression like the following with 12345 being your target and…

Be as generic as possible, because even if you're starting small and all teams are working within their own buckets (projects), there will come a day, where cross-functional (cross-project) work (or statistics) is needed. And then, you don't want to have 'In development' from the development team, 'In documentation' from…

Thanks for this helpful summary!

Hey @Chris Buzon , Not actually a 'problem' query but more of a monitoring thing I use on a regular basis, is the 'Two Dimensional Filter Statistics' with a grouping by project and resolution in order to determine which resolutions are still in use and which ones can be potentially removed to unclutter the system. The same…

Hi @David Peles , Are you referring to doing that check on manual issue creation? If so, you'll need a workflow app that provides validators based on Jira expressions - see https://marketplace.atlassian.com/addons/top-rated?category=Workflow Cheers Thorsten

Hi @Marcus Woller , You should be able to head over to your approval step in your workflow and hit 'Configure' at the 'Add approval' option in the right sidebar. Within the popup, you can decide whether all approvers are needed or just a specific number: Cheers Thorsten

Comprehensive overview, thanks @Dave LIAO !

Hey @Gabriel Deal , I'm with @Daniel Ebers here - most likely the field is actually not empty? Is the field still visible on an affected issue? If a custom field is empty, it's no longer shown in the issue view.

Hi @Murthy Indian Forever , confirming what @Alex Koxaras -Relational- already suspected. In addition, see https://jira.atlassian.com/browse/JSDSERVER-4789 and watch for further updates. Cheers Thorsten

Hi @s_vanleeuwen1 , could you please head over to the workflow currently in use for your 'Epic' issue type and check for validators being present at the initial 'Create' transition? If there is one provoking this message (probably requiring a value for the 'Epic link' field), please remove this one. However, ensure that…

Hi @Roshan Vislavath , while it's not possible to 'translate' the email address automatically, you could go for branch rules (if we're only talking about a small number of possible - and future - assignments since this will obviously not scale), e.g. * Your trigger * Branch rule #1* Condition - text field equals/contains…

Hi @Marek Kákoš , running Server, you'll need an additional workflow app that provides a 'Fields required' condition or validator (usually they provide both then) - see https://marketplace.atlassian.com/search?category=Workflow&product=jira As an example, Jira Workflow Toolbox being one of them has a generic 'Fields…

Hey @Gabriel Deal , once you clear your field (completely), it shouldn't be returned by that search you've mentioned anymore. Could you please provide additional information regarding the custom field type? Is this a classic or a next-gen project? Cheers Thorsten

Hey @Doug Slay , could you please - when in doubt - add a screenshot of your configuration? Please ensure, that you're using the correct syntax, especially regarding our field code reference - see https://apps.decadis.net/display/JWTSDC/Field+codes That said, your expression should probably read: %{issue.cf10002} != null…

Hi @Priyanka khare , you can add the following property to your restricted status: * Key: jira.permission.edit.user * Value: yourUsername However, I'm with @Joe Pitt doubting this really is a 'best practice' approach. May I ask which action this automation rule is supposed to perform or how exactly your use case is? Cheers…

Hi @Albert Manuel , in order to rearrange the order of your transition buttons (those are transitions, not statuses), you should look for the opsbar-sequence transition property -…

Well-written article. I will definitely give it a try.

Hi @Jurica Petricevic , components are related to the project and not the issue type(s), so you're not going to be able to 'hide' certain components for certain issue types. If you want to restrict a field to your sub-tasks, you should consider switching to a dedicated custom field and restrict its usage/availability to…

Hi @Athos Online , since your '2nd column' is related to another status, what you're trying to achieve is actually an automated transition for your incidents. Without further knowledge of your specific configuration or workflow, the approach would be as follows: * Trigger: issue created event * Condition: issue type equals…

Hi @Meghana , if you're about to add the new type 'Request' to your project, you'll have to add it to your issue type scheme, that's correct. However, if you remove issue types from that screen, you'll definitely have to migrate issues with removed issue types to ones still available. Changes here aren't only related to…

Hey @Lance Moonshower , if you're not going to further use the app, you should uninstall it via the 'Manage apps' section and remove the remaining gadgets from existing dashboards. Cheers Thorsten

Hey @Lance Moonshower , it seems like you have trialed our app sumUp for Jira (see https://marketplace.atlassian.com/apps/1211625/sumup-for-jira?hosting=cloud&tab=overview) and now the trial has ended. In order to continue to use the app, you'd need in fact a license. If you have further questions especially related to the…

Hi @Amruta Pelapkar , yes. You'll obviously have to add the corresponding field to the edit/view screen.

Hi @Amruta Pelapkar , while you can not enable or disable a status in a workflow (add or remove steps), you can do so with the transitions between those statuses (control the way an issue is able to take). That said, you might need to add conditions to your transitions as shown here: The default Value Field conditions…

Hi @Brett Palmer , thanks for the feedback. Would you mind accepting my answer then? Thanks in advance!

Hi @Brett Palmer , in order to to do further troubleshooting I probably need 'the full picture', e.g. the exact expression used. Are you able to share?

Hey @nick while this might not be possible without an additional app, Jira Workflow Toolbox being one of the potential ones includes the functionality to do just that - see an example configuration here: https://apps.decadis.net/display/JWTSDC/Move+an+issue+to+another+project Disclaimer: I'm part of the team behind the…

Hi @Brett Palmer , while the hint from @mfabris is definitely correct as well - please use ~ instead of = - I'd like you to note that after adding this field to an issue, running a JQL statement against the actual value isn't working before another issue updated event or project/Jira reindex has taken place. Cheers Thorsten

Can't wait to welcome Cloudie! Thanks @Kyren Wong

Hi @Vivek Patel , since setting the due date is tied to the 'Schedule issue' permission, you could revoke this permission from your developers (role) while still granting them the 'Edit issues' permission. That way, your developers can still edit issue fields while not being able to adjust the due date anymore - see…