Tuncay Senturk _Snapbytes_ Community Champion

Hi @Jeffrey Bistrong I'm not sure but what I'd do is to test removing jira-core product and try if it works. As you may already know, Atlassian has recently deprecated jira-core as a standalone product and now it's bundled into jira-software. So, I'd suggest using "products": ["jira-software"] instead, even though the…

That's weird. Not sure but does the issue creation involve an issue type or operation that triggers a move internally? It may be automation, script, post function 

Hi @Asif Fayaz S In JSM cloud, removing a person with an admin role does not undo or break the configurations they made. However, if any rules were created by that person and configured to run as them, they may fail when the user is deactivated. You need to check Automation rules. If they created shared filters,…

Hi @Prathap DL You can have a workaround making specific fields read-only in certain statuses, but in this way you'll lose the inline editing function. Steps to the workaround - Remove fields from the regular Edit screen, all those fields will be readonly - Create a special Edit transition (self-loop), - Add a condition to…

Hi @Riccardo Barbieri I'd suggest posting this question on Atlassian Developer Community, I'm sure that you'll get more answers there.

Hi @Ben Manifold Custom fields are absolutely supported in JQL. 200 error indicates a bad request, even for admin accounts. It may be due to field value mismatch, so I'd suggest checking the exact value using the Jira UI. First test the JQL in Jira UI. The customfield_12998 may not be available in the context for the…

Hi @Nitin Pai This usually happens when the sender (the reporter who creates the ticket via email) does not have a Jira account. You have already noticed that some reporters do not have Jira accounts. If they do not have a Jira account, Jira defaults to using their email address. When creating tickets via email, the…

Hi @ilya Could you share more details?

Hi @Mateusz Janus Sometimes fields like Due Date don’t update right away because Jira relies on indexing for calculated fields and JQL searches. Only updated issues get re-indexed automatically, so unchanged ones may show outdated values or be missing from filters (like in BigPicture). To fix this, you can manually trigger…

Hi @Jay Boyd I can say that the hyphens are not part of native Jira behavior. Jira Cloud does not automatically prepend hyphens to issue summaries. As @Stephen_Lugton mentioned, it can be because of custom Automation rules. An automation rule may be modifying the summary field. Or a third party app may prepend those…

You're very welcome!

Yes!

Hi @Ian Rickwood If you upgrade your free plan to a paid plan, you can request a site URL change through Atlassian Support, without needing to create a new site.

Ohh!, I would not find that. Thanks for letting me know. Yes, Jira is sensitive and case sensitive :) 

Hi @Aisha M I'm well, nice to hear from you :) I'm not sure if the problem is related to that but I'd suggest two things at first glance. 1. reindex the issue after the migration if (newStatus) { Status destinationStatus = constantsManager.getStatusByNameIgnoreCase(newStatus) workflowManager.migrateIssueToWorkflow(issue as…

Hi @Roan Roodenburg That's weird, as I tested in several environments and it works just fine. I've also checked and haven't seen any changes that removed issue key searching from the board, as @Piyush Annadate _ACE Pune_ mentioned. Have you tried reloading the page or doing a clean refresh? Sometimes client-side Javascript…

Hi @Purnima Maganti You need to provide more information. Have you checked your server logs? Did you see any log like Server started at port 8095 If not, it means it hasn't started properly. I trust there is something in the logs that can help us gain a better understanding.

Hi @Chetan_N You're right, the Two Dimensional Rich Filter Statistics gadget only shows issue counts—it doesn't natively support displaying percentages. The reason for this could be that the gadget totals counts across the two axes, and showing percentages might confuse whether the percentage refers to the horizontal or…

Did you try to inject the OptionsManager using the constructor? import com.atlassian.jira.issue.customfields.manager.OptionsManager; YourClass(final OptionsManager optionsManager) { this.optionsManager = optionsManager; }

I don't have a github repo but I used that class in some of my private plugins and they worked fine. However, when adding the dependency "jira-core" I used to get a library conflict problem which I solved by adding an exclusion as below <dependency> <groupId>com.atlassian.jira</groupId> <artifactId>jira-core</artifactId>…

Hi @Rajit Kuthiala Did you try using your own wrapper class? I mean instead of referencing com.atlassian.jira.issue.customfields.impl.MultiSelectCFType directly in atlassian-plugin.xml, create your own class that extends it (as below) MyCustomMultiSelectCFType extends MultiSelectCFType Then use it in your…

Hi @Rajit Kuthiala Could you share your pom.xml's related part as well as the stack trace that you are getting?

Hi @csordasmarci - trigger: field value changed (Cost) - I'd also recommend adding a condition: issue type = sub-task , so that we'd ensure the rule only runs for sub-tasks. - add a branch rule / related issues, type: parent inside the branch - action: lookup issues - parent: {{issue.key}} - edit issue (parent), field to…

Hi @MahmoudShehabat Check if this post is helpful.

Hi @Andrea Sloan I'm not 100% sure but it may be because of the issues that are associated with multiple Sprints (for example, an issue was started in one Sprint but completed in a later one). The most recent active Sprint is displayed by default. For completed issues, Jira collapses this field to show something like:…

Hi @Anshuman Ankur I think creating a support ticket for the Deviniti team is best.

Hi @Jongho Jung The REST API response for invalid JQL queries includes detailed syntax error messages by default. There is no setting to globally suppress or customize these error messages. You can use a reverse proxy filter to intercept API responses with these status codes and a body containing "errorMessages" etc and…

Hi @Toby Moore Unfortunately, JQL doesn’t support extracting or comparing just the month from a date field without year. However, you can use Automation to achieve this. This is what I'd do : Create a single-select custom field, e.g. Reminder Month Define a Jira Automation to update the field whenever your date field…

Hi @Christian Lakin Dick You can add the Estimation field to the Create Issue screen. As @Marc - Devoteam mentioned, you can make the field required. Making the field required on the create screen may not be possible; in that case, you can add a validator (Field Required Validator), which will prevent issue creation…

Hi @Mary.Hernandez Since your coworkers aren't experiencing the same issue, the problem might be specific to your user or setup. have you tried reauthorizing jira in your Slack?