Comments
-
There's no way to add buttons, only web-fragments (links)
-
I don't know, you have not explained what you want this correspondance to do or how it should work or appear to your people.
-
During a post function, you have direct access to the issue object that the post function is currently running against. So while you can get the key with just issue.getKey() You don't need to, because you can just directly use the issue already! You "def issue =" line would be overwriting an object you already have.
-
In the 5 years since this question was asked, Atlassian have done that. See Jira Cloud.
-
You'll need to get an admin to either grant you access or debug what the problem is.
-
It's hard to tell without seeing your code.
-
You have no choice - you can only amend the menu with a "separate plugin" See https://developer.atlassian.com/server/jira/platform/web-fragments-4227124/ for doing it in your own plugins.
-
No, Atlassian are not going to add another field that does what a multi-select already does. If you want people to add free-format options, use a label. If you want a restricted list, use a multi-select.
-
Nope, no change!
-
User = an account that Jira is aware of Concurrent users = people making the server do work at this time You might have 1,000 users, 500 active and able to log in, but the concurrent users are anonymous people and the number of the 500 logged in - those clicking on stuff/typing/using REST Every user account, active or not,…
-
See https://confluence.atlassian.com/adminjiraserver/specifying-field-behavior-938847255.html
-
I have not found one yet.
-
No, you can't do this directly - the service desk project must be hosted by one or the other Jira instance. But, you can set up synchronisations between projects on each server, so that activities on one server are mirrored (precisely or with variational procedures such as "project 1 has a field that is not in project 2,…
-
No, the whole point of the labels field is to allow people to create new values. If you want a limited list, the best you can do is use a multi-select.
-
Because of the things I said in my answer.
-
Not sure that you would need to look at the Bitbucket code for this, but you can get it by going to your my.atlassian.com account, finding the line for the Bitbucket server licence, expanding it and using the "download source" link beneath the licence key.
-
See https://confluence.atlassian.com/jiracoreserver/configuring-dashboards-939937983.html and https://www.atlassian.com/blog/jira-software/5-steps-to-build-a-killer-dashboard You don't need to be an admin to create dashboards, just the permission to "create shared objects" if you want to share them
-
In that case, the types you had at the FAA were provided by apps that added more project types.
-
As above! It's not changed.
-
An issue can go through more than one sprint, so I suggested a look at all the possible values - the single value you've got there is clear. This issue does not look "done" to me. Is "User Testing" in the last column of the board?
-
I can't solve this without knowing how your data got damaged (if it is) Could you pick on one of those issues and go to the plain issue view. Can you check what status, resolution, story point and sprint value(s) you have for it?
-
This will only work if the two issue types have the same field context - that is, custom field 11513 is the same field on both issue types (so if they're a select list, they have the same list of options). This means the field itself is the same on both issue types (whatever the actual content, the field is the same, and…
-
Those types have sub-types, but my guess is that the FAA used Cloud Jira, and your new place does not. The sub-types list on Cloud is a LOT longer (but still fixed)
-
None of the missing issues in the sprint report appear to have a status, which implies something has really done a LOT of damage to your Jira data. You haven't touched the database or run scripts that might affect these issues?
-
I think you have a damaged workflow in the database. When you say "I click workflows" - what do you mean? Admin? Issue view? Project admin? I say because you probably need to work out which workflow it is and delete it, and there's ways we need to explore to find it first!
-
Components are a part of projects, not a way to control access. The closest you can get is to automate something that sets a security level depending on Component set, but that could easily get very complex and messy.
-
They can't create spaces, that's the job of a Confluence administrator. They can create Service Desk projects, groups and custom fields. Basically, they can do everything the system admins can except the exclusions - the list of "can do" is far longer than "can't"
-
This is something "field configurations" do - they provide a list of fields and you can flag them as mandatory if you want to force them to be entered on create. However, they are mandatory throughout the life-cycle of the issue - must be filled in on create, and cannot be blanked out, and they are independent of each…
-
I didn't say confluence groups, I just said groups. It doesn't matter where they came from - usage is determined by who can log in, and that's controlled by the groups named in global permissions.
-
I'm afraid that is a must, yes.