Comments
-
Go into each space you want to make public and add the "anonymous" flag to the permissions. See https://confluence.atlassian.com/display/DOC/Assign+Space+Permissions
-
Yes, click "search"
-
>The field vallue is set by a custom plugin. Best guess is that the value, while being set by the plugin, is not being indexed correctly. Try re-indexing and see if that improves the situation.
-
I don't understand the requirement, sorry. Do you mean you want to force data into a field? The user should never leave it blank? Make the field mandatory will fix that.
-
I'm afraid your question is unclear. Does what notify the the user? What do you expect from "exclusive"? I'm guessing the status is that you want to know when the status changes?
-
Follow the first four detailed steps above. They make it possible to have different groups with different accesses (the default setup does NOT let you do this, you MUST change it) Once you've reconfigured the access system to support the locking down of your user groups, all you have to do is go into the roles for a…
-
* Add them to "Jira users" group so they can log in. * Make sure the "jira users" group does NOT have the "global permission" to "browse users" * Add the "Jira users" group to a role in that 1 project that has the permission "browse project" (You may need to create a new role for this, and update your permission scheme) *…
-
That usually means that you're running it twice. Not easy to tell though. The advice it gives you is solid - you need to read the logs for more detail.
-
I think you've run into this issue - https://confluence.atlassian.com/pages/viewpage.action?pageId=596181603
-
No, the component list is a multi-select, not a cascading select. It doesn't categorise components either - there's no data structure to allow you to do that.
-
Go to your my.Atlassian account which you used to buy Cloud Bamboo and add more users to the service in there. You don't need to contact support for that unless it's not working for some reason.
-
You don't. You are right about where the data is coming from, but there's no way to change it without amending the code (and you can't even add your own plugins to OnDemand, let alone change code) On the human side, I'm interested to know what you'd like to see as the page title? I think Atlassian would be interested as…
-
No, it needs to know who someone is so it can tell them about responses.
-
What customisations have you done to it? What's the JVM and version of Jira? Are there other errors in the log? Has it run ok before, and if so, what have you changed between the last run and this one?
-
You can send "subscriptions" to groups, but the groups have to be ones JIRA knows.
-
That was asked and answered yesterday. https://answers.atlassian.com/questions/293441/jira-and-confluence-use-the-same-users
-
I've seen a number of attempts at scripting and coding, but they're all very specific to the sites they're on. However, have a look at the backbone sync add-on: https://www.k15t.com/software/backbone-issue-sync
-
Er, have you read the error you've posted here? It specifically states that you have not given it user details that can connect to your database. The solution is to ensure you've set up the database correctly, and give stash the right credentials.
-
Actually, I suspected that, but I've seen it called other things and used to mean totally the opposite. The language is not standard, so it's worth checking. That is answered on the licencing docs, although Atlassian have a slightly more fluid licence scheme than most "named" because you can deactivate users to reuse their…
-
What do you mean by "named" or "concurrent"? Have you read https://www.atlassian.com/licensing/jira ?
-
That is something you have configured in your JIRA, it's not something we can help you with. Your JIRA administrators have set it up, you'll need to talk to them. (Could be a service, an Automation plugin trick, or a 3rd party add-on providing a script)
-
You don't need to do any of this, if you really do mean just "I want my users to be able to find their issues by the old id" Try this: * Create issue ABC-123 * Move it to project XYZ * Use the url http://yourjira/browse/ABC-123 or type ABC-123 into the quick search You'll find Jira recognises the old reference and takes…
-
No, the document is currently correct. Contact Atlassian support for help in migrating.
-
You seriously need to stop trying to synchronise the ids. Even your comment "changed with no side effects" is probably wrong - I can think of two things that could break spectacularly as a result of that change unless you've also made matching changes in other places. Using the ID to match options is absolutely the wrong…
-
It's a lot more complex than what you've found here. Changing the ID of a custom field in the database is a recipe for a disaster - you have to know exactly where it might be used and check and change all those places. You've found three, I can rattle off 11 and I know I'm missing some more. General advice - if you ever…
-
Volodymyr, despite saying he's not sure, is, as usual, right. It's not possible directly. When you import, JIRA uses its standard sequencing - each new item gets the next number. You can store your IDs in another field, but if you need to keep the absolute numbers, you are going to have to create an import that has all the…
-
Correct - the 2d filter gadget can only handle "stattable" fields - that is, fields that are effectively fixed length lists. You need to be able to look at the list of possible values and say "there's X of them" It's arguable that a date is a fixed length list as there's about 365 dates a year, but text fields, numbers and…
-
You'll need to write a listener plugin to do this (or use the Script Runner, which allows you to code without having to write a whole new plugin) I've said to use a listener because that can detect and run on any event you chose to trap. It sounds like you probably want to trap "edit" and then check the status and custom…
-
Yes, issue for the issue counter. The project counters are in the project table though. This is exactly why you should use the importers - you don't need these details if you use them, and they're going to do a better, faster, safer job than you having to work all of this stuff out for yourself.
-
Ahh, good. No, "sequence_name = action" is probably for the ID of the next comment. I can't remember which entry is for issue id. But yes, that's the table that keeps the counters in it (there's quite a lot of counters - fields, custom field values, comments, workflows, schemes, etc).