Comments
-
What add-on?
-
There's no way of knowing this. Atlassian gather operating system information when support calls come in, but there's no real attempt to gather an accurate list - I've worked with hundreds of Atlassian systems and raised support calls for less than 1% of them. In my experience, you're looking at 80-90% running Atlassian…
-
Ah, good. That actually tells us that I'm probably right. Jira is (frustratingly) dropping the column from your original filter because you are including the possibility of issue types that do not have the field at all. The fix here is either 1. Run separate filters - one with the issues that have the field, and a second…
-
What test have you done? What works?
-
Mmm, I would not expect that to be the problem here. If it's the field visibility as I expect, then the field being mandatory is completely irrelevant, because it effectively doesn't exist. Could you try the test I suggested to rule out my theory?
-
Oh, that sounds like your query includes the possibility of returning issues where the field is not valid. Note - not "empty" - those are fine, but not "having a context for this project/issuetype" If you do that, Jira will silently drop the column from your results. To test this, pick an issue that does definitely have a…
-
Just move the fields in the screen definition from one tab to the other. I've no idea why you think you're getting separate notifications - the email system effectively ignores the tabs - a change to an issue is a change to an issue, it doesn't matter what tabs the fields are on.
-
That is what I said, yes. However, if you want to do tasks and sub-tasks at the same time, then you need a different approach. You won't have a list of tasks with existing JIRA ids, so in your CSV, you need to show which is going to be the parent. I wrote it up at https://answers.atlassian.com/questions/12280942 although…
-
You need to provide each line with an issue key under which it will become a sub-task
-
Ok, you'll need to write a one-off script to iterate over the options for the first field and add them to the second. You'll need to get a FieldConfig for both fields, then use it on the first field to get the list of options. You can then use <span class="memberNameLink">optionManager.createOptions</span>(fieldConfig,…
-
I'm not understanding the requirement here, it's one of two things. Do you mean: You want to copy values on issues from the subsystem field into the impacted-subsystems field OR You have a list of options set for subsystem, and you want to add all the current options there into the list of options for impacted-subsystems…
-
That is a totally different question. It's also one you can't do though. Issue types are limited by the PROJECT you are in. That's it. The best you can do is block issues from being created, after the user tries to do it - put a validator (again, script runner is your friend!) on the create transition that can say "if user…
-
You can't. Some people try it with javascript, but that's an ugly hack that people can easily bypass. The best you can do is remove "priority" from the edit screen, then find/write a validator which you can put on transitions - you can code it to see if the priority is changing to "critical" and then check if the current…
-
Make sure that the filter for the boards include the the issue in some way.
-
There's two possible problems here First, you've allowed all of your users "create" rights. That's why all of them get the full list of "projects I can create this issue in". I would remove "jira users" from all permissions except the global "can log in". In fact, I never use Jira users for anything other than "can log in…
-
You've got something that allows your external users "create" permission in the non-external projects. Check the "create" permission in the permission scheme(s) associated with the non-external projects. I know it's a little odd having the rights to create issues in projects you can't actually see, but it can be useful.
-
Themes are installed globally and then made available to the whole of your Confluence system. You can then choose which one you want to use for each space individually.
-
I'm not sure quite what you're expecting here, but assuming that you need something changed on Cloud, you need to contact https://support.atlassian.com . It would probably help to give them details such as the email address and domains.
-
Could it be failing because the parent issue is not created by the time you get to the subtasks? I think that might cause a validation failure with no actual results (it used to in version 3)
-
Yes, you can use the customer credentials to do things with the API. You'll need to explain what your code is doing when it tries to authenticate, and give us the full error message.
-
That's a "captcha" - see https://confluence.atlassian.com/doc/configuring-captcha-for-spam-prevention-169970.html
-
Create issue and comment are NOT workflow conditions, they are handled by the permission scheme. Also, conditions do not "deny permission for a group", they are "allow" based. If you don't want a group to do something in a condition, then you have to make sure the members of the group do NOT fall into a group that can do…
-
I think you need to expand on this question
-
No. Cloud does not yet do LDAP. If you want to connect LDAP, you have to use Server.
-
Yes, see https://confluence.atlassian.com/doc/connecting-to-an-ldap-directory-229838241.html
-
What errors are you seeing? Logs and on-screen?
-
The "Jira Toolkit" has a "Participants" field - holds commenters, assignee and reporter.
-
Posted this in completely the wrong place. Sorry!
-
Rather than post links and expect people to read another system, please explain the problem here. Most of us won't bother following links.
-
Really sorry, misread that completely. But I think I can see a problem - I think you're trying to fetch an object that the system is generating on the fly. If you use a browser, the system is going "ah, ok, I need to build that from the data, give me a minute.... ok, here you are". But curl and wget simply grab the object,…