Tuncay Senturk _Snapbytes_ Community Champion

Hi @Art Hsieh It is hard to guess what the problem is but I'd say non-developer users will not have access to Forge functions until the app is installed in the Jira instance they are using. If you are testing in development or staging, the app must be explicitly installed to that Jira site. forge deploy --environment…

Yes, you can get all issues assigned to a specific user by this REST https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-jql-get /rest/api/3/search/jql?jql=assignee=username

Hi @goekce.vardar1 As far as I understand, you want to automatically assign tickets to the correct sprint based on their due date. You can use Jira Automation to achieve this. afaik, Automation doesn't let you dynamically search which sprint contains a date but you can use if-else conditions for each sprint as a…

Hi @Dan C Have you heard from the JiBrok team yet?

Hi @Nhật Đăng Lê Unfortunately saved filters or persistent views are not supported, afaik.

I see, you upload correctly but the transition API call fails due to temp attachment ID. I'd suggest uploading the attachment using asUser() instead of asApp() — since the transition call is made via asUser(), Jira expects the attachments to be uploaded by the same user session in order to see the attachment ID in the same…

Seven trouts, a glowing tent – that sounds fantastic. I have neither fishing experience nor a story to tell. The only thing I could catch there would be a cold :D 

Hi @Ankit kharola Sorry, I'm confused. Are you getting invalid json error or are you able to ad the attachment? 

Hi @Bogdan Ilchyshyn I've checked the Atlassian Status page and couldn't find any issues apart from an invoke on issue view failure. It could indeed be a bug or a regression, I'd suggest submit a support request or ask this question on Atlassian Developer Community.

Hi @Emilia KASPRZYK In JSM, you can automate recalculation with Automation, see this article. Other than that SLA calculations are event-driven, meaning that when you update an SLA definition, only new events like issue updates, transitions will trigger the new rules. Existing issues retain their SLA even if closed.

Hi @Jill Tunick You don't need to delete the entire SLA and create a new SLA from scratch. You just need to click Edit on the existing SLA. Then click into the JQL condition field (which is highlighted red in your screenshot) and delete priority = 1 and type severity = 1 or whatever your severity levels are. e.g. severity…

Hi @Ritik Thawani If you're trying to implement OAuth 2.0 in Laravel, I'd suggest to use Laravel Socialite, if you are not doing already. the “Access Denied” issue you mentioned—does this happen after the user is redirected to the provider and enters their credentials? If so, it could be due to incorrect redirect URI, or…

Hi Do you see any error logs in the console or the Forge tunnel output? What’s the exact behaviour you're observing — is uploadFilesToJira being called successfully? Also, are you seeing a response from Jira’s /attachments API, or is it failing silently? You have to provide more information :) By the way Atlassian…

You're absolutely right! I just wanted to check because I thought it (advanced branching) might expect a list of objects and using split might convert it to an iterable list. So, I'd suggest: - create a variable first (let's say name: codes and the value is as the below)…

Hi @Samuel Imrich Would this work? {{issue.description.match("[A-Z]{1}[0-9]{3}").split(",")}}

Hi @Ankit kharola Could you please provide a bit more detail about how you're trying to add the attachment? For example, are you using the REST API, Forge, Connect, or some other method? Also, sharing any relevant code snippets or error messages would help in understanding the issue better.

Assume you have a team of users A and B. First rule: your JQL will check the first five checkboxes, and the assignee will be A. Second rule: your JQL will check the last five checkboxes, and the assignee will be B. The method (round-robin or load-based) will have no impact if there is only one assignee; however, if you…

Hi @Sandesh TM adding a simple change event lisneter on an input field would be something like the below code in javascript AJS.$(function () { AJS.$('#customfield_XXXXX').on('change', function () { // what will you do when you got the change console.log('Date changed:', AJS.$(this).val()); }); }); I don't know what have…

Hi @Prabhashankar Rai You can achieve this by using smart values and conditional logic. For example, you can loop through the selected checkbox options and use if/else branches in your automation to assign specific assignees based on the selected items' position (e.g., first 5 → A, next 5 → B, etc.). However, this setup…

Hi @Cedacri You're right, there is not one function that fits all. So, you have to handle all, let me list what parent can be for each case and then try to code accordingly case 1: Sub-task → Parent (.getParentObject()) case 2: Story → Epic (.getEpic()) case 3: Epic → Parent ('Parent Link', this is a custom field) case 4:…

You're very welcome!

Hi @Janek Schumann It is best to raise a support ticket here. I am certain Appfire will advise you on how to take action as soon as possible. 

You must grant the user write permission. Otherwise it can't create folder/file.

Thanks!

Hi @MT I trust that by posting this question to the Atlassian Developer Community, you will receive more answers. As far as I know, - atlassian-rest-common is deprecated and you can replace it with Jersey 2 or REST modules provided by Jira. - embedded-crowd-core, it's not recommended to depend on directly, you can use…

Hi @Sachin Guttala as far as I know, validation on issue transitions based on linked issue status is not directly supported out-of-the-box. However, if you have Script Runner you can do this using Scripted validator wit a script like the below ( I used resolution field but you can change it with the status.name != 'Closed'…

Hi @jira_admin_cu You can create your "monthly-reports" folder under your JIRA_HOME and store the report files in this folder. Here is the code that may be helpful for this. def jiraHome = ComponentAccessor.getComponent(JiraHome.class); String localHome = jiraHome.getLocalHomePath(); String folderPath = localHome +…

Wow, what a wonderful story @Kristján Geir Mathiesen ! Apart from my primary school years, I'd say my Maths teacher Mrs Arzu Ozcan in Samsun, Turkey. She was a fantastic teacher and also a great supervisor. I’m truly grateful for everything she taught me — her way of explaining complex ideas so clearly really stayed with…

Hi @Dharanyaa Balasubramani It is best to raise a ticket to the vendor through this support portal.

Hello @Singh Yes, this is definitely a workflow issue and it is a very common situation. Jira considers an issue unresolved if the Resolution field is empty, even if the issue is in a "Done" status category. Define a transition into "Complete" (or any Done status) with a post function that sets the Resolution field, and…