Comments
-
What does the log say the problem is?
-
No, you can't do that, columns follow the sort order of the board.
-
No, it needs all those steps.
-
Quick filters are a function of boards. For a gadget to do something similar, it needs to implement code to provide the function, which is what the apps you have found do. I'm not aware of any apps that replicate the server apps you've found on Cloud.
-
I can't give you "another option" as the field is not set up correctly. The only "option" is to fix the configuration.
-
If you can edit other fields on the issue, then the problem is most likely to be that the priority field is not on the issue's "Edit" screen. (Other possibility is you have an app doing some form of security on fields - we can't know if you've got that) If you can't edit the issue at all, then yes, it's your permissions.…
-
Any upgrade might change APIs, but we can't be sure because you have only given us half the information - you need to compare the start version and the new one. Best bet is to read the release notes for each version from the current one to the new one. Note that APIs rarely change significantly while you're in the same…
-
Yes, that's absolutely right. You should set a resolution when you finish or close an issue. (You should also, ideally, clear the resolution if you re-open an issue). You can do this automatically though. Edit the workflow and do two things * Remove the resolution field from the transition screen * Add a post-function to…
-
Subscriptions are handled at filter level, not in your profile. Log in as normal, go to "issues and filters" and go to the bottom of the menu for "view all filters". Find the one named in the email (Sorry, I don't know how to do Cyrillic here, but the line includes "have not updated in 12h" in your screen shot), and from…
-
No, the issue type is determined by the project settings.
-
When you're working in a place where you have a project context, you don't need a "current project" function because you already have it.
-
I don't think there are many around - most of us use the built-in "create issues from highlighted text", or issue collectors.
-
Could you check what is different with these issues and the ones that are appearing ok? If the search you have given is not returning them, how do you know they are in the sprint?
-
I think you are confusing "swimlanes" with "columns". * Columns are columns on the board, collections of issues grouped by their status. * Swimlanes are rows running across the board, grouping cards in columns by almost any criteria you want. Assuming you mean columns, not swimlanes, then your question comes down to the…
-
Use the priority in the SLA definition - see https://support.atlassian.com/jira-service-desk-cloud/docs/create-service-level-agreements-slas/
-
It's not hard to do, it's impossible. You can't tell what the current project is in my worked example because it does not exist. If you assume "all projects", that's fine, but useless, as that's what Jira is already assuming. The closest you can get is "last project", and even that is not particularly useful. Imagine I…
-
Ok, so try this: * Log in. * Go to "issue search" * Tell me what the "current project" is at this point?
-
I am afraid we can't tell you. You have an automation or script making this change, you need to find it and reconfigure it
-
It's from 3 years ago when there was a different system in place.
-
It won't be quite the same as Portfolio, but you can replicate some of it in Structure.
-
You will need an app to supply fields like that. There are a couple of attachment-field apps in the marketplace, but I've never used them, so don't have a specific one to suggest.
-
I've solved this with Scriptrunner - you have your "estimate entry" field as a drop-down, then have a scripted field that reads the value from the field and presents it as a number for the estimation statistic.
-
I would very strongly recommend that you do NOT do this. A list of custom field options that gets too long (and it will in this case) will rapidly become useless to users and then start hurting performance if it continues to grow. Could you explain why you are trying to do this? Of what possible use is it to the end-users?
-
This code would work right up until the last line. The custom field will not return a string, it will return a list (collection/array etc) of user objects.
-
You would need to have the code in Jira to put back in a display of the name instea of the icon.
-
You get that when you have not selected a value in the field's configuration settings. Have a look at https://scriptrunner.adaptavist.com/latest/jira/script-fields/database-picker.html
-
How did you set the Epic to "have a parent link"?
-
To see a project, a person must match the rule for "browse project" in the project permission scheme
-
I am afraid repeating the phrase I have asked you to clarify does not help Can you please tell us what you mean by "refer to another issue" and what you mean by "text box to search another issue"?
-
It sounds like you are allowing your "customers" to sign up as full Jira users (which consumes a licence) rather than just the standard customer level sign up. Have a look through…