Comments
-
Sometimes this doesn't work, not sure why. I reproduced it in https://community.atlassian.com/t5/Jira-Service-Desk-questions/How-can-I-remove-portal-only-customers-from-a-specific-project/qaq-p/617234
-
It may be that your DB just won't do more than 12, I would check the config there. I would also add that JIRA rarely has any issues relating to DB throughput unless you have a huge instance.
-
There is a much simpler short term workaround while you implement the correct, and long term more sustainable option which other authors have suggested. * Create a new group * Put user in group * Put group into Jira Users global permission * Grant user access to project via Roles.
-
I would suggest you ask this at https://community.developer.atlassian.com
-
Did you update the server.xml file to specify the proxy url?
-
There are a number of third party apps that bring this kind of functionality to Jira. Take a look at two I found after a quick Google: https://marketplace.atlassian.com/plugins/com.gebsun.atlassian.rtasks/cloud/overview https://marketplace.atlassian.com/plugins/pl.com.tt.jira.plugin.theschedulerpro/cloud/overview
-
It looks like this is not possible at this time: http://help.trello.com/article/1049-slack-app You may want to take advantage of Send us feedback /trello feedback I love tacos!
-
Thanks for being so transparent with this.
-
look at jirasoftware150917151933-stdout.2017-09-18.log and look for DB related errors.
-
You can try to use a JQL function like this https://confluence.atlassian.com/jiracoreserver073/advanced-searching-functions-reference-861257222.html#Advancedsearching-functionsreference-latestReleasedVersionlatestReleasedVersion() with a != operator.
-
Are you developing your own add-on? If so, you may want to look at: https://community.developer.atlassian.com Otherwise, can you tell us on what website and where in it's UI you are seeing the above error?
-
Yes, this works fine if you use the CSV importer https://confluence.atlassian.com/adminjiraserver073/importing-data-from-csv-861253680.html
-
No, native issue ranking is a global value. However, you can use a customfield other than Rank, and populate it with values yourself and have the UI sort by that field. I don't think that Drag and Drop to rank will work if you do this.
-
This is being discussed at: https://community.atlassian.com/t5/Jira-discussions/Are-you-an-Atlassian-Certified-Professional/td-p/641875
-
Check to see who is the project lead, and also look at your components to see if they are configured to assign to the old user.
-
Synchrony needs to run on a port that is different from Confluence. If Confluence is using 443, then you can not use 443 for Synchrony. If you look at https://confluence.atlassian.com/confeap/administering-collaborative-editing-847355676.html you will see a section at the bottom about changing the port. It says: Synchrony…
-
I am also one of the early certified people, and also a co-author of one of the tests. As Atlassian Partners, it is necessary to maintain that relationship. It shows Atlassian and their clients that we have the knowledge and commitment required for them to list us as Partners. I have had 1 recruiter approach me so far…
-
You will need to look in your JIRA logs for the exact error message. It will be in the <installdir>/log/catalina.out file.
-
Why not just use checkboxes for both? You're relying on issue history for auditing either way. You may may consider using two user picker fields instead with transitions to approve into the second field. It makes it enforced by who users actually are, not just a trust that the change history will save you.
-
Custom fields can do this I think: http://help.trello.com/article/1067-using-the-custom-fields-power-up
-
What are your custom field types?
-
Click the ... in the upper portion of the done column. Click on "Archive All Cards in This List"
-
https://confluence.atlassian.com/adminjiraserver075/changing-jira-application-tcp-ports-935391759.html will allow you to change the port it runs on.
-
Only needs project admin https://confluence.atlassian.com/agile/jira-agile-user-s-guide/releasing-a-version-kanban But it has to be for all projects which fit into the version. You likely need to tighten up the JQL powering the board.
-
How large are these repos? Have you tried this: https://confluence.atlassian.com/bitbucketserverkb/git-ssh-push-timeout-on-large-changes-779171775.html ?
-
I marked it as not spam for you.
-
https://sparkmailapp.com/
-
Draft automation isn't enabled I think? Also you need to make sure that the user that Automation is working as has permission to make the transition. Verify that this isn't the issue by removing your validator during your test.
-
my face got flagged as spam :(
-
On issue update / edit / whatever other events if status in (anything after your approval needed status) and status was not in (your approval status) then transition to Open specifics will obviously differ based on your workflow