Andy Heinzer Atlassian Team

Hi Jon, For some background as to why this is happening please see The Upgrade to Atlassian Account. If we haven’t upgraded your users yet and you have a password policy, you must verify your domain to keep your policy. I would recommend taking a look at that referenced Atlassian blog post: Domain verification From that…

Hi Markus, It looks like you already found the solution here, if other users should have this same problem you will need to first allow these anonymous users to do this via the project's permission scheme. Managing project permissions has details on how this can be done. Thanks for updating the post to provide your…

Hi John, There have been changes recently to the Cloud API. They are cited in the KB article you linked to: User management REST API changes in JIRA Cloud Update user PUT /api/2/user This request can only modify the "active status" of the user Passwords included in the request payload will always be ignored This particular…

In JIRA, attachments are not bound to comments, but rather to specific issues in JIRA. There is way add attachments in JIRA via REST, the endpoint in JIRA is /api/2/issue/{issueIdOrKey}/attachments https://docs.atlassian.com/jira/REST/server/#api/2/issue/{issueIdOrKey}/attachments-addAttachment

The drag and drop feature in JIRA won't work with images/files taken directly from another browser window or tab. The drag and drop feature is intended to allow you take files you have stored on your local filesystem and make them attachments to a JIRA issue. So it's not just you, but also I would not expect your exact…

That can be tricky to do when migrating data from another issue tracker. What method are you using to import this data? Are you using a CSV import to make this work? If you already used a CSV, then this method would be easier to accomplish. There is a guide on the site on how you can create a CSV file to reference specific…

JIRA does not have a native means to edit attachments on the fly in the browser. You can edit attachments and then re-upload them after changes have been made. But in those cases, you would have to save the file to your local filesystem first anyways in order to then make changes and upload it again. Perhaps you would be…

Hi Raul, You can activate both a Core and a Software license on the same JIRA instance. However you will need to segment the application access for each group of users, and you would need to make sure that each group that is granting application access does not exceed the license count for that particular license. That…

There is a document on this specific kind of workflow over at Incident management - Atlassian Documentation.

I believe this is actually expected behavior. In JIRA there are a number of default behaviors like this where you cannot assign issues to users that have been created in JIRA, but have never logged into the system. I think this is a designed safeguard to prevent inidviduals from assigning issues to an account that has not…

In JIRA try navigating to Cog Icon -> System -> Outgoing mail. Here are defined the settings for sending mail with JIRA. I would want to confirm that your "From Address" matches the actual account name being used below in the username for authentication. If these don't match, then I would expect your SMTP server to get…

This same question was asked in the post Is it possible to configure the default Story Points field to be a Drop Down List? On that post, @Nic Brough -Adaptavist-replied with a way where you could use a separate select custom field, that could be restricted with certain values, and from there it might be possible use…

If anonymous users can create issues on the main JIRA site, then you would need to modify the permission schemes in your JIRA instance in order to change the "Create Issue" permission to no longer include the "Anyone" value. Managing project permissions - Atlassian Documentation has the steps on exactly how to do this. But…

This is not something JIRA can do natively. But there are plugins that can extend this functionality in workflows. For example the JIRA Misc Workflow Extensions does have the ability for JIRA to add specific fields to a validator before you can then execute a transition that would change the status.

It looks like this same kind of question was answered over on Solved: Which Database table stores User Profiles? - Atlassian Communities From that post @jing_hwa_cheokadded this SQL query to locate that information from the SQL database: SELECT OS_PROPERTYENTRY.string_val, CONTENT.USERNAME FROM OS_PROPERTYENTRY INNER JOIN…

You can create a parent or master board like this that contains all the issues from the other boards/projects. But this could be problematic if you do. The steps to do so would be to first create a new saved filter that includes all the issues that exist in the other four boards. Depending on the complexity of the other…

You can do some of these natively with JIRA alone (numbers 1 and 3). However #2 can't be done with just JIRA because natively JIRA does not have a way to relate parent to child in this way via JQL. That is something that can be done if you happen to have scriptrunner though. Scriptrunner has some scripted JQL functions…

At the moment within JIRA, there is not a way to add requested participants via automation. There is a feature request for this over in JSDSERVER-3628 As such I believe the same is true for removing users via this method as well. However there is a KB that you could use to add users, provided you use the scriptrunner…

The only time I have seen this specific problem is in regards to a plugin in JIRA that can cause this specific behavior. I understand that you have already tried another browser like Chrome and this does not happen there. But it might be worth trying to temporarily disable some of the user plugins in JIRA to see if this…

Sorry there is not a way to do this in the customer portal of JIRA Service Desk yet, but there is a feature request for this over in https://jira.atlassian.com/browse/JSDSERVER-4636

Not sure if this problem is still ongoing. If this was a fluke, then https://status.atlassian.com/ could have indicated if the marketplace site was down during that time. If that site is up, then the problem is more commonly seen to exist on the machine/network running this JIRA server instance. The most common cause for…

Hi Goran, It appears that you also created a support case on this issue as well. This is the recommended course of action here. There actually is not much that you could do here as the end user of a Cloud instance to address this problem, short of removing unwanted attachments of course. The limitations of attachment…

The subscription method to accomplish this would be the most configurable, but it would not provide real-time results. The subscriptions in JIRA are just running a saved filter search to find issues in JIRA, and then emailing the results to a user/group at a set interval. First you need to create a JQL filter and save it…

This was a known bug in that specific version of JIRA Service Desk. Please see https://jira.atlassian.com/browse/JSDSERVER-4720 for details. This was fixed in the 3.3.2 release.

You could try to use a number of different charts in JIRA to try to show this data. I would recommend trying the "Created vs. Resolved Chart", since you are focused on the creation date of these issues, that should help to see how often they are happening. You would need to create a JQL saved filter, such as createdDate >=…

JIRA Software does have some native reports you can use to track this information. I would recommend taking a look at https://confluence.atlassian.com/jiracoreserver073/reporting-861257295.html That page does describe a number of reports including the "Time Tracking Report" that can help with this. If that's not as…

JIRA does not currently have a means to do this in a Kanban board. There is a feature request for this over at https://jira.atlassian.com/browse/JSWSERVER-6254 However time tracking and estimations are not as important to the kanban ideals as they are inside of a scrum agile method. I think that from reading over…

Are you using the native CSV export in JIRA 7.2 and higher? Or are you using a 3rd party plugin in JIRA in order to export this information? It sounds strange if you can only intermittenly repeat this with the same data being exported. There is a known bug in JIRA's native CSV export method if the data being exported…

There is a documented bug on the inability to get the issue collector to load correctly in an iframe, please see https://jira.atlassian.com/browse/JRASERVER-45229 However that bug page does note a work-around for this: Adding this to the HTML page that has the issue collector should resolve the problem:…

You could try to look at the Burndown report to see what issues might have been added to the sprint after the start. These would be registed as a scope change event in this report and you can see this even when the sprint is active. https://confluence.atlassian.com/jirasoftwarecloud/burndown-chart-777002653.html