Comments
-
I think in 3, Hartmut means that "sprint = 754" has been typed into the search box in the UI. It should return the same as 1 (and your corrected 2), but if it does not, then we should compare the different results to have a look at the issue that appears in one search and not the other.
-
Sounds like you have lost either the database or the home directory, and possibly both. There's no point proceeding with an attempt to re-install or recover until you know what has done this damage and why. Check the system logs to see what has been done.
-
Jobin means you should tell your people what and how to do things, rather than try to deal with it in JIRA. Most of us have a JIRA support project, with a "project" type issue type so that users can quickly ask the admins for a new project. For large installs, some of us automate the process, so that new projects are…
-
The doc says "If you have more than 2 rows returned per custom field, there may be a serious corruption on the LexoRank table. Please contact Support for further help. " Get in touch with them at https://support.atlassian.com/contact
-
You will need to write a listener that gets the content of the multiple-project field and iterates over the content - I expect a "get custom field value" call to that field will return an array, with each element being a project.
-
Short answer is "yes". It is reliable, it does scale (and as you've said you have BB datacentre, you've got full support for the largest of systems). However, while I am an Atlassian fanboy and would love to be able to tell you that BB is the best possible solution, I can't. I do not know the competition well enough to…
-
Click "log work". You need to have the project permissions set up to allow you to do that, so if you can't see it in the menu, check the permission scheme for the project.
-
Start with the project settings page and look for "field configuration scheme", you should be able to drill down from there.
-
No, that's not what I said. Your base url should be the url you want to access the system on. It doesn't need "mapping". Look at your hosts file on the server. For Linux it will be /etc/hosts You need to make sure that is correct. Specifically, what does that say for any lines that contain "localhost"
-
Not without a lot of coding - characters like that are not valid in uri's and have to be used with % escaping and Confluence only generates simple uris without encoding.
-
You don't. When the resolution is placed on a screen, it takes a value, and unresolved/none/blank is not an option. You need to make the resolution optional, and remove it from all screens except those on "close" type transitions.
-
What does the log say is going wrong? (It should contain that error a long with more detail)
-
Try a different filter - "resolution = unresolved" will get you all issues for every project that are still open. A blank filter will select everything.
-
You can use issue links (cloning issues will do that automatically, linking the new issue back to its source), but these will not be parent/child relationships like you get from sub-tasks.
-
You'll need to tell us what you heard of to get any further with it - The documents Branden pointed you to cover the Atlassian options, and most of the approaches using non-Atlassian stuff.
-
Yes, Atlassian released a new layout for Cloud a few weeks ago. See https://community.atlassian.com/t5/Confluence-discussions/What-just-happened-to-Confluence-Cloud/m-p/622890#M237%3Futm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_reply&utm_content=topic for some discussions about the changes.
-
Search for the issues, and save the search as a filter (a filter like "project = X" or maybe more usefully "resolution = unresolved) Add a "filter statistics" gadget to the dashboard, and select your saved filter, and "assignee" as the thing to report on. You won't get users with no issues assigned in there, as you can't…
-
JIRA Server and Cloud do not have corresponding versions. For any Cloud export, the best bet is the latest version of Server. If you've got an old export like you have then go for the latest version that was available on the date of export - see https://www.atlassian.com/software/jira/update
-
Only if you've got the "premium" support package. If you don't, then you'll have to go through the support portal like most of us - start at https://support.atlassian.com/contact
-
issue.getDueDate returns a "time stamp" object which can go straight into the custom field's modified value.
-
It looks like Xamarin doesn't document how to build with Bamboo specifically, so you're a bit stuck and will have to work out what you need to do for yourself. (Atlassian can't document every possible use for Bamboo - it's designed to be used by any form of build process, so there's simply too many, and Atlassian only have…
-
It might not be the exports/backups directory that it cannot read/write. It uses temporary caches and temp directories, so it could be one of them, and it might even be the attachments directories its trying to write. Does the error not say what it was trying to do?
-
If the requirement is to make something go through both "sub flows" before moving on, then yes, absolutely use sub-tasks (and a condition on the main issue saying "can't move until sub-tasks are done). It's one of the things they are for!
-
Yes. Just drop the idea of "sub flows" as it's irrelevant. Whatever your processes are, just put them into a single workflow that takes two separate routes until joining up on status A.
-
Sorry, I missed your first response. It's not the add-on I was thinking of. It looks like the electronic signature add-on which requires you to enter an extra password when "signing" an issue. I don't know why it might be used during logging work though, might be worth raising it with support for that add-on.
-
Your screenhot says you are not an admin. That suggests you have not got the user directory right when you upgraded. I can't help you with that without knowing what you had before, and what you changed.
-
>I find that all the issues of the new instance which connect to the slave DB canont be viewed JIRA requires full read/write access to its database, and it requires a full re-index after any change made to the database that does not go through its API. You can't have a slave database in write mode, and re-indexing your…
-
Same question as https://community.atlassian.com/t5/JIRA-questions/How-to-add-quot-Links-quot-field-to-the-list-of-X-Y-axis-in-a/qaq-p/634509?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_question&utm_content=topic
-
Your permissions for the space do not allow you access. As a space or system admin, check the space permissions.
-
The most likely explanation is that your hosts file is set up incorrectly. Check the localhosts mappings and ip address.