Comments
-
Ah, sometimes you have to do that - some of the post-functions don't load into the display when they hit dead fields, and when that happens, you can't delete them! Well spotted!
-
We're a community of end-users of Atlassian software, not support, although we do try to help. In the first case, you will need to talk to the administrators of your system to ask them why/if their email is not arriving!
-
I wonder where you're getting that question from, because * It's not brilliantly written (several of the possible answers are wrong for more than one reason, making them easier to rule out for people who are certain, but seeding doubts for the rest of us) * The answer they've given you is utterly wrong. The right answer is…
-
If the boards are in the same system, then yes (although you don't "move between boards", you change the issue so that the current board no longer selects it, and the other board starts to. Often this is just by moving the issue from one project to another using "move") If they're in different systems, then no, they're…
-
Yes, I know you don't - that's why it's saying customfield_10814. It's trying to look that up, but you have deleted it so it can't find it, and hence displaying the (internal) reference to it instead of the actual name. You need to edit or remove the validator or post-function that is trying to use the deleted field.
-
I'm a bit stuck - I think you are trying to do this: >all groups to display when the users from those group got assigned to that issue its has to display the user belonged group name in that group field But that does not make sense. Could you explain it for me?
-
One of your administrators has added a post-function or validator to the "close" transition. This was configured to check or work with a field that has the id 10814. The field has been deleted by an admin. You need an admin to go into the workflow and update or remove whatever it was that was looking at that field.
-
It's not a lot of use to get the exact version because * Cloud is always "latest" (within a 4-6 week window) * Cloud updates frequently. If you gave someone the current version today, it could be wrong by the time they read it, and certainly will be in a couple of months. But, you can get it from "help -> About"
-
You don't add custom events to a transition (without code), but you can change the existing system post-function to fire a different event, including any custom ones you've added. Edit the transition again, go to post functions and you should see "edit" next to the existing "fire event" function.
-
Ok, I think I've skipped explaining something - the screenshot you've given us is of the history, not the "view" of the issue. The history records what the options were at the time your change was made, not what they might be now. Could you check the value of the custom field in the issue *view*, not the history tab?
-
Your script is not applying the change you've put into the mutableissue object. https://library.adaptavist.com/entity/update-the-value-of-a-custom-field-in-jira has some stuff about applying changes
-
Ask your users. Technically, you can add tens of thousands. In real life, your users will stop using it if you add too many, and "too many" is way lower than the technical limit.
-
You are confusing the function "watchers" with the project role you have added called "watchers". The project role "watchers" has nothing to do with the list of users on the issue in the "watchers" section. People in that role are not watchers. They are people who have some function in the project. Watchers are individual…
-
I'm afraid a snippet of error message, without any context, on a 5 year old question that does not seem to be related, is not a lot of use to anyone. Please could you ask a new question, including the context and tell us why you think it should work (as all we can tell from the error is that you've not got the right…
-
If you use a standard "user picker" custom field, you can tell it to list users from a group or role in the project. I'd probably set up a "designer" role to use for it!
-
I am afraid I do not understand the question - could you give us more context? Where did you read this question? If it is one of the exam questions, what were the other options? I ask because the answer you've been given there really sounds wrong - it would only be the right answer if the other 3 (or more) options were…
-
No, that's the opposite of what I said. You have 2000 users allowed to use Jira, so you need to licence add-ons for all 2000 of those users.
-
It's an English word descended from the Latin "re" meaning "with reference to". Mostly used in legal documents and a lot of email systems prefix it to email summaries to indicate that the email is a reply to something (so "re: email notification" means "with reference to: email notification")
-
Ok, you have the numbers now, so you know where to truncate or split any over-sized fields you are copying from Assembla!
-
It's not between Scrum and Kanban. It's between those who see subtasks as pointless noise in the backlog (it's nonsense to rank them there, so why bother), and those who want to see them. Solution - accept that they are of no use in the backlog, and use the "links" field to display them if you still want to see them.
-
This usually happens when you start Jira as the wrong user (e.g. root), which takes ownership of lots of files, then try to restart as the correct user, who no longer has the rights to remove the files. Stop Jira, check and correct file and directory permissions and ownership, then restart it as the right user.
-
Why? Your users won't remember, and if they go over them, the system will either not let them over-fill the field, or tell them they can't commit oversized strings. But generally 254 and 32767 are the two limits for short and long text.
-
You have to buy a licence for all users who are allowed to use it - that is the number of users allowed to use your Jira.
-
You can't "fix" it because it's not broken. You can't change it on Cloud (and I wouldn't try it on Jira Server because you'd have to rewrite the core code). Text fields are limited by the code to match the smallest allowable text field in the standard databases (i.e. 254)
-
That display shows you have a slow network, or possibly that you're running a poorly configured Jira and/or an underpowered server.
-
See https://developer.atlassian.com/server/jira/platform/rest-apis/
-
It works fine, but it is past end-of-life and hence not supported (any problems or security issues with it, you will need to upgrade)
-
You need to check if the Tomcat that supports Confluence is running first. "ps -ef | grep java" is a simple way to find that out. If it is running, you need to read <confluence home>/log/atlassian-confluence.log to see what is wrong, although if that says nothing, you might need to read the catalina.out that you've already…
-
Neither of them list a vulnerability that would allow remote execution of packages that could contain ransomware. I'm afraid it got there via some other route.
-
When you add css to Confluence spaces or layouts, it is standard css, there's no "confluence variant"