Tuncay Senturk _Snapbytes_ Community Champion

Since you have suspended the user, you need to reactivate. Go to Jira Administration > User Management and find the user and reactivate the user. Fir the permission scheme, I think you are on free plan and permission schemes are not available. If that's the case, go to People under the project settings and ensure that the…

Seeing the user while mentioning in the comment does not verify that the user is assignable user for an issue in that project. You need to check project permission scheme.

Hi @Govardhan Reddy Have you checked that the user has the necessary permissions to be assigned issues? Check permission scheme and verify if that user has "Assignable User" permission for the project(s). You may need the project role/group of the user as well. Also check if the user has got the application permission.

That's good news! I am glad you were able to complete the installation.

Hi @Dimitrios Kouroumichakis I don't know which solutions you've tried and why they haven't worked but you could do it by creating an Automation rule. I tried to write necessary parts of the automation rule below, I hope it helps - Choose Issue Commented as the trigger - add Issue Fields Condition (field: Status,…

Hi @Joris BAUDOT There are no incidents identified on Atlassian Status. This is likely due to your personal settings. Please check your personal settings to ensure that email notifications for issue updates are enabled.

Hi @Kawan Diogo It looks like there are missing database tables (pluginstate and moved_issue_key). For some reason, Jira didn't fully initialize the database during the setup and that reason needs to be fixed. I'd suggest - verify your db connection settings and connect to the database with the credentials in your…

Hi @Cristian Acevedo As far as I know, Jira Cloud does not provide an option to add users without an email (also without sending an email). There is a ticket registered in Atlassian. You can vote for the ticket JSDCLOUD-4935 

Hi @Dhananjay Sharma The error suggests that the Component field is required, it can't proceed because this field needs to be populated during the creation. You can either make the Component field optional or add a default value to avoid this error.

I'm glad that you had a workaround. Thanks for sharing.

I see. Is Time Tracking enabled for the project? If this feature is disabled, you may not be able to see the option to log work.

Hi @Лёня Криволапов Your configuration seem fine at first glance. Is there a reason you don't use the Log Work action instead of making a web request?

Hi @Alexandr Unfortunately, JSM does not provide a direct way to get a complete list of users who are using REST. Please take it with a pinch of salt, have you tried looking at the atlassian-jira.log file as I believe it has entries for such king of REST usages, something like below 2025-01-27 11:44:22 exec-3 INFO username…

Hi @wiwan I don't know what went wrong with given link but I listed what I'd do for your case: - add a trigger "Field value changed" and select the fields: Start date and Due date - add an action: Branch and Choose "Parent" - add an action to update the parent task's dates: -- Start date: the smart value to find the…

Hi @Maéva In order to retrieve the value of a custom field from the child issues, you need to use the lookup Issues action. First add an action lookup issues action with the JQL below "Epic Link" = {{issue.key}} then add log action with the smart value as something like below {{#lookupIssues}}{{Story…

Hello @Dean Ayres Your code seems OK, but let's try a different approach. Create a variable and set it with the random value and then use conditional logic on the variable. - Add an action Set Variable and set the variable with {{RANDOM()}} - add another action and use conditional logic as below…

I'd suggest raising a ticket to Atlassian support (https://support.atlassian.com/contact/) 

I see, I am unsure that it is because that it is locked as I recall I use locked fields in filters. Sorry, I wasn't helpful.

Hi @Ingo Bultschnieder Sorry for the misunderstanding. Have you checked the issue contexts (Settings > Issue > Custom fields), it may be restricted to a project or issue type which may prevent displaying for unrelated projects or issue types.

Hi @Ingo Bultschnieder Does your app store the text in the field or just fetch and display it in Jira? In order for Jira to index the field, it must have data stored in a way that Jira indexes for searching. We need more clarification (maybe your manifest and code related parts) in order to understand. Actually, Atlassian…

Hi @Stefan Bombrowski I also checked the new API and could not find an appropriate use for the attachments directory. I believe the Atlassian Developer Community will be a better place to ask this question, as you may receive more answers there for this sort of development questions.

Hi @Hieu Nguyen There may be several root causes for this error. Did you try forge tunnel? Do you get a similar connection error when you use tunnel? As the error states, Forge apps do not work directly without being embedded in the Atlassian context. However, I trust you have already configured the Bitbucket connection…

Hi @ossarchitect There is no bundled and ready solution for that. However you can achieve that with either Automation or using an app. Automation: - First create a custom field (text field), "Most Recent Comment" - then create an Automation rule, trigger: Issue commented, action: Edit Issue, field: Most Recent Comment,…

@Nissim Ariel Click on the "Your work" top menu item, and you should see Boards tab link

Hi @Nissim Ariel Yes, it is possible to use the same sprint for multiple projects by creating a shared board that includes issues from multiple projects. Go to Boards and create a Board, selecting Scrum Board. Choose the option create a board from an existing filter (filter containing multiple projects). Then you can go to…

Hi @Victor Tobon Your code seems OK, considering the fact that you set up a token and use for your connection. For the rest, let me try to give you some snippet which may lead you to the right point. def response = new JsonSlurper().parseText(connection.inputStream.text) def members = response?.members?.values?.collect {…

Let me try to boil it down. My solution requires using Automation. - Create an Automation rule (Project settings > Automation > Create Rule) - Choose Issue Created as the trigger - Add a branch/action and choose edit issue fields > more options (advanced json) use the json I provided replacing the 12345 with your Customer…

Your understanding of the baseUrl is correct. It must remain publicly accessible because Atlassian Connect uses this endpoint to load your app's resources (connect-json, index.html, etc.). This is mandatory. baseUrl and any endpoint defined under it must be accessible over the internet. You can host only what is necessary…

Hi @Michael Krarup Stefansen Pulling out the customer email domain from the Description field is easy but it may also come with other problems, e.g. if there are multiple emails in the description field, etc. I'd suggest - create a custom field to store the domain (say it is Domain: customfield_12345) - then create an…

Hi @Navdeep Singh You can host your backend (HTML, CSS, js) in a private repository instead of Github Pages. This way your code will remain private and not exposed publicly. Atlassian allows Server/Data Center apps to be packaged in a .jar or .obr files, but this is not applicable for Connect apps. You can deploy a private…