Gor Greyan Expert

Hi, @Abi Williams Yes, the disappearance is certainly from the configuration in your project's board settings or workflow conditions. You can check the following configurations. 1. They may be conditioned on the appropriate transition. Check the workflow transition conditions. 2. Each column has mapped statuses; if someone…

Hi @Audra Bonacki Thanks for the provided screenshot. May be the issue from the List View. Can you check it via Detail View?

Hi, Dear @Israel Gonzalez Caballero After the review, please also accept the answer if it is helpful. :) 

Dear @Evgenii Thanks for the answer. But that is not fit for me. I can't do it via different instances, as I need one instance, which will have different sub-domains for the Portal. But thanks for the reply.

Hi @Israel Gonzalez Caballero , Automation doesn't support issue cloneing from one instance to another, also that Clone action is cloneing ticket inside the same instance. You can use the following akternatives. 1. Using Send Web request action and using Rest API to create ticket in 2nd instance. 2. Using 3rd part plugins…

Hi @Vojtech Raba , As of now, Jira Cloud doesn't support built-in theme switching on dark mode in Help Center and Customer Portal. You can enable dark mode using browser tools. Also, there is an open ticket in Atlassian, you can track and vote :) https://jira.atlassian.com/browse/JSDCLOUD-13227

Hi @Audra Bonacki What kind of custom field was it? Do you have a script under it, or was it a field of one of the plugins?

Dear @Saranraj Sampath Thanks for the provided answer. Let's try with the following one. { "fields": { "summary": "Test", "issuetype": { "name": "Sub-task" }, "parent": { "key": "TEST-123" }, "priority": { "name": "Lowest" }, "project": { "key": "TEST" } } } And please inform me, do you have chance, to do the import via…

Hi @vanwilder As I know, Gantt chart doesn't support random sorting of groups. But you can try the following alternative, if it is fitted to you. Instead of random ordering, try creating a custom field, where you assign numeric prefixes manually. Example Values. 03 - Alice 01 - Atur 07 - Mary Then try to group by this…

Hi @Durga Solse Try to review the following apps, they may be fitted to you. https://marketplace.atlassian.com/apps/1235710/simple-timesheet-export-free-worklog-generator-for-jira?tab=overview&utm_source=chatgpt.com https://marketplace.atlassian.com/apps/1222051/status-time-reports-free-time-in-status

Hi @Enrique Carrasco Try checking it via the Audit Log. Go to. Secuirty --> Audit Log Category = User Management, Action = Suspend User You will see the timestamp and the actor who did it.

Hi @John van Ginkel If you mean the default Jira date picker calendar, unfortunately, it is impossible. It is fixed to a monthly calendar view.

Hi, @Ali Demir Try the following. <a href="{{issue.url}}">{{issue.key}}</a>

Hi @Saranraj Sampath Thanks for providing JSON. Your JSON creates sub-task, but Jira doesn't know which parent issue it belongs, because the "parent" attribute is missing. You should specify the "parent" key with the issue key or ID of the parent issue. Try with the following JSON. { "projects": [ { "key": "Test",…

@Erick Díaz Thanks for the provided alternative. Will use if needed.

Hi @Steve Beauchamp , Jira's native JQL can't compare fields against each other. For your case, you can try to reach it via automation. 1. Trigger- Issue Created 2. Condition for the issue type: Issuetype = Task 3. Branch Rule: Parent(Epic) 4. Compare parent's customfield to {{issue.created}} 5. Action: Set customfield…

Hi @Avi Ziv Try to review the following one. Azure Blob + Explorer

Hi, @Saranraj Sampath Thanks for your question. Could you please share a part of your JSON, in order to set how you import that.

Hello @Erick Díaz You need to filter sub-tasks based on their parent issue’s sprint. Unfortunately, JQL doesn't support native parent-child filtering across custom fields like Sprint. But there are workarounds: I can suggest 2 solutions. 1. If you have ScriptRunner, you can try the following JQL. issueFunction in…

Hi @Mauricio Carvalho _ Suporte I have a similar situation, when my sprint is being started, I get the Remaining Estimate and keep it in the Planned Estimation field. I could achieve that via the following. { "fields": { "customfield_21809": "{{#=}} {{issue.fields.timetracking.originalEstimateSeconds}} / 3600 {{/}}h" } }…

Hi @Jeanne Howe Am I right that you get an error when trying to add Epic Name into the Issutype A?

Dear @jessica_huebner , thanks for the interesting question. If you have JMWE app, you can user "Field Requires Vaildator" with the condition, like the provided screen. If you don't have third-party apps at all, you'd need to redesign the workflow slightly using multiple transitions and validators.

Hi @Leanna Bremenkamp , I am using the lookupissues via the following way and it is working, try like this. {{#issues}} <a href="{{toUrl}}">{{key}} </a> | {{summary}} <br> {{/}} In the end, add this {{/}}. Let me know if there is any information.

Hi @Tim Lee Try adding user from the User Management interface but not assign them to any project. Assign the project only after first log in. As I know, there is no possibility fully disable it through UI, it is not a configurable customer notification. In the Data Center, when creating a user, there is checkbox, "Sent…

Hi @Ana Luiza Chagas , def fieldA = issue.fields.customfield_XXXXX // Replace with Field A ID def fieldB = issue.fields.customfield_YYYYY // Replace with Field B ID // Logic: if Field A is "Yes", then Field B must be filled return !(fieldA == "Yes" && (fieldB == null || fieldB.trim() == "")) Try the following script in the…

Thank you too, @Maggie D.

HI @Maggie D What did you get after clicking on it? As it works fine on my side, after clicking it redirects to the tickets list with that label.

Hi Dear @Norlin Md Noordin , Setting the "Resolution" field to Unresolved, doesn't actually clear it. Jira considers any non-empty value in the Resolution field as meaning "resolved". Unresolved is typically a placeholder used when the field is empty, not a value that should be set manually. Solution. You should clear the…