Andy Heinzer Atlassian Team

Hi Stephen, It looks like you created a support case on our customer support portal https://getsupport.atlassian.com which is what I would have recommended in this case. For our Cloud sites connecting to each other there should not need to be any changes made to application links to make this work, but I think there might…

By default JIRA doesn't change the issue priority during a transition. It's only expected to change the issue status. But this is something that you can configure. It's not a board setting though, instead this is something you would need to configure in the workflow settings for this project. If you have not modified on of…

There was a lot of feedback on this feature in Service Desk. In the next version of 3.5, they added more granular controls over what to do with that CC field when Service Desk is processing such emails. More info on this in the JSD 3.5 release notes. I suspect that this group distrobution list is getting added to service…

In JIRA Server, changing the avatar in your profile does not automatically reload the page. So while your avatar has been changed at that point, the avatars seen on the activity stream have not been reloaded yet. You can simply refresh the page after making this change to have those update as well.

Portfolio is trying to help address common bottlenecks that teams get stuck on issues that they cannot complete and do so in the planning stage. Since your team doesn't have any members with the needed skill, there is no way that team could be expected to complete that specific task. That is why you get this warning. The…

There is an existing bug documented in JRACLOUD-61831 about this. This effects instances using the default language of Portuguese. There is a work-around for this where you can change the first letter of month to lower case (08/jul/16 4:00 PM).

It is not possible to use that specific field outside of a Service Desk project. Instead of that field, you can instead use the Watchers field. It provides the same feature as Request Participants. The difference is that JIRA Service Desk needs Request Participants option in order to allow JSD Customers (that do not have…

When JIRA fails to startup like this, there should always be an error in the JIRAHOME/log/atlassian-jira.log and/or the JIRAINSTALL/logs/catalina.out that should be able to tell us more information about why this startup failed. If you have no such logs, or these do not update when JIRA is called to start, then I would be…

I was actually able to use this same character 👨 in a quick filter in my JIRA instance. Although this character is technically a 4-byte character, it might be a unicode character too, but that isn't the aspect that causes the problem I'm thinking of. There is a known limitation specifically that effects JIRA instances…

Is this a Cloud or Server instance of Service Desk? If this is a server instance, then what version of Service Desk are you using? I can't seem to recreate this behavior in the current versions. I did find some very old bugs from Service Desk 1.x versions, but they appear to have been fixed long ago.

Natively JIRA can't create a notification for a specific value of a custom field. It can send notifications on an issue edit, but it isn't able to look at specific field values alone to make this notification event happen. But there are ways that you might be able to do this with plugins like scriptrunner and use a custom…

Java applications like JIRA and Bamboo take their system timezones from the host operating system. So one way to fix this would be to change the operating systems to all use the same timezone. Alternative to this would be to the KB article: Setting the timezone for the Java environment. This KB explains that you can leave…

It is possible that these subtasks do not have a value listed for "Fixed Version" field. Try assigning these issues a value for that field. Most Kanban boards will still show issues on the board that do not have a fix version value.

You can do this if you edit the permission scheme of that project in order to change the "Create Issue" permissions. You will probably want to remove at least the "Service Desk Customer - portal access" group from that permissions, and perhaps other users/groups/roles as well. That would prevent the creation of new issues…

JIRA does not natively have the ability to do this currently. There is a feature request for this over in JSWSERVER-2360. While there are some suggested work-around in the comments of that page, I found a related post over at…

JIRA does not natively have the ability to do this currently. There is a feature request for this over in JSWSERVER-2360. While there are some suggested work-around in the comments of that page, I found a related post over at…

Have you updated the Base URL in JIRA to reflect this change to https? I would also check to make sure that the server.xml JIRA is using has the correct proxyPort, proxyName, and scheme parameters defined in it for this connection. The server.xml settings are important here, and JIRA does have to be restarted after these…

Component fields in JIRA are expected to show all the possible values for components in that project. If you have entries here that are not used, you can delete these component options from the project administration page. That is the only way I am aware of to limit the results on that drop-down box.

Did some digging for this question; to the best of my knowledge there does not appear to be any limitation on the number of levels a hierarchy can have within portfolio.

Certainly you should not see a blank page there. But the error log seen so far do not appear to correspond to this particular problem. That error in the log just means that the JIRA server itself is unable to connect to the base url JIRA is currently using. It could be because the system can't resolve that hostname to be…

This error is very generic and doesn't give us a specific cause for it. However usually this error can happen when bamboo is unable to connect to the database being used, or the database is not configured correctly. Are you following the Bamboo installation guide in order to complete this installation? I would also be…

1) Yes, you can absolutely run JIRA on one server and the database instance on another. You just need to make sure that JIRA can reach this database over the network. If JIRA ever is unable to contact that database server you can expect JIRA to fail. We would also expect the database instance and the application server to…

Is this JIRA Cloud or JIRA Server instance? If this is JIRA Server, what versions of both JIRA and Tempo are you using? If you're seeing an option to subscribe, it makes it seems like the plugin is installed, but that it might be unlicensed and in turn not functional. If this is JIRA Server, I'd be interested to see what…

By default, JIRA Software does not populate any version values in the project. You will need to create the versions on a per project basis. Steps on how to do this are in Managing Versions. Once you have some versions defined there, then you can update an issues in JIRA to either populate the Fixed Version or Affects…

I think this is actually by design. I understand that you would like to see that estimate update when deleting a story from a sprint, but once you start the sprint, the estimations at the time the sprint are started are actually expected to not change. You can add or remove items from a started sprint, but to do so does…

Changing the context of a custom field in an existing project is expected to have the ability cause data loss on that field. I would recommend taking a look at Change Context for an Existing Custom Field Without Losing Old Data. That KB explains how you can create an entirely new context for the same custom field to use in…

Hi Cris, That link you posted Manage application access - Atlassian Documentation is actually for our Cloud platform. You can see this in the specific URL as well. I am afraid that the Cloud versions tend to be very similar to server versions, but our Cloud platform tends to get newer features way before Server does. Also…

Hi Nick, Sorry to hear about this problem. I was also able to reproduce this same issue. I don't think this is something that permission schemes are going to be able to solve right now in Portfolio. I agree with you that it doesn't make sense as to why these JSD customers are even an option here. But at the moment, there…

The JQL query is going to return all issues in project XXX that were also in any sprint that is now closed. However a sprint in JIRA can be closed without completing all the issues in the sprint. Also an issue could have been in multiple sprints. So I'm not sure if ths information helps. Could you let me know why finding a…

This can be difficult to answer. All of these products can either manage users locally, or can connect to an external LDAP/AD directory, or both. So failed login attempts for LDAP accounts could lockout the account in LDAP for any/all of these applications. But to be clear, it's the LDAP instance that is actually locking…