Comments
-
I don't quire understand what the question is. One of your Atlassian accounts is named as a technical contact for your systems on my.atlassian.com, so you should be able to see the licences and contact details there. If there are no paid licences, then you are either looking at the wrong systems, or your vendor has not…
-
You can't. You're effectively asking to see issues you have chosen not to see. It's one or the other. If you want to see an issue on the board, it needs to be selected by the board to be visible - the board filter needs to select it and it needs to be told in what column to appear.
-
Again, bad idea, and it's not valid for Cloud.
-
No, "losing page revisions" is something Confluence is explicitly designed not to do. It versions every change, that's what it was built for.
-
It's the same answer - please show us your workflow scheme and then an issue that has the wrong workflow on it, ensuring you show the project headers so we know it's all in the same project.
-
Your error message does not match what you're posting - check the custom field number again! Also check you are logging in ok - try to fetch a whole issue and see if that says you can see it.
-
You've misunderstood what the REST endpoint in ScriptRunner does. It allows you to write an endpoint that does what you need it to. You could easily code an endpoint that responds only with the Status ID and nothing else when it is poked with an issue ID. You don't do any work on your side and a handful of lines of code is…
-
@somethingblue, who answered originally, is your best bet.
-
I'd strongly recommend not doing that. Jira's database is a data store, not a reporting model, and you certainly can't write to it.Could you explain what you are actually trying to achieve for the end user and why the custom fields can't already do it?
-
No. Community is forum software, not an issue tracker. Https://support.atlassian.com is a Jira issue tracker, with Service Desk, so you're raising "requests", which are a front-end for issues. I'd suggest using Service Desk if you want to catch user issues.
-
That does not sound like a broken index. You can test this though - pick an issue you want to link to and edit it. Add a , or . to the summary or description. Are you able to search for it in the link screen now? If you can, then yes, its indexing. If you still can't, then it's not the indexing.
-
I really don't understand this. Popping up a screen with a resolution on it is an incredibly simple standard function that we all use all the time, and it ships in some of the default workflows. What happens when you try the following? * Create a new screen * Put nothing but the resolution field on it * Create a new test…
-
Ok, that's great, very clear. If you hover over the Admin you've surrounded in orange, does the tooltip say display/userguide/admin ? Could you rename it to something else and check what url is shown when you hover as well?
-
You say "2. When the user clicks it, ". Where, exactly, are they clicking? I can see where it lands them, but could you look at what link your users are using to get it (mostly, you can hover the cursor over a link to see the url it will take you to in a tooltip)
-
Yes, if they are acting as customers.
-
Ah, I see, thank you! Use the search - https://developers.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-query-issues You should be able to build a query for "customfield_x ~ your key"
-
The scrum boards show open sprints, as you sometimes want to move items in or out of them. Kanban doesn't have sprints, so you don't need that There's no point in having in-progress things in a backlog - by definition, a backlog is stuff you have not started. You might as well forget the backlog if you're just going to use…
-
Your account here is an "Atlassian account", but you might have another one which is tied to your work email address (I've got two I use a lot as well) You should log into my.atlassian.com with whatever account that was named as the technical support contact.
-
Do you have any "Behaviours" defined in the ScriptRunner add-on?
-
Go back to admin -> custom fields -> <participants> -> Edit, where you changed the name of the field. The searcher should be selectable below. Check that there is one, the field might say "none" if there is nothing selected.
-
I suspect it's because in-progress items are, by definition, not in the backlog - you've started work on them, so they're on the board.
-
I'm afraid you have simply repeated the question in much the same way, and it is not clear from that what you are looking for. Let us forget REST for a second, could you explain what you would do as a user in Jira to do this? What would you go to and enter?
-
Not that I know of. I suspect you are expected to ask your admins not to create too many.
-
When you renamed the field, could you have changed the searcher for it accidentally?
-
Many more than will confuse your users! There's no particular limit to the number you can create.
-
As it's unassigned and inactive, I'm afraid Atlassian are not working on it. Open does mean they have not ruled it out though. And I know they're working on revising the way fields are attached to projects in general.
-
You don't. You need to log in as a root user and change the password to something you know. And if you want to log in as the user, change it from a locked password to an interactive one.
-
This usually happens when people put the jira-config.properties file in the wrong place, or leave it with the wrong ownership and/or permissions. Check that it is in jira-home, and is owned and permissioned in the same way as other files in there.
-
By definition, an admin needs to be able to get to the administration section of a project, whatever state it is in, or they can't do their job. You should find they can't see the project anywhere else, but admins need at least the admin section.
-
Make sure it's optional in the field configuration.