Comments
-
You can't do this, and you don't want to anyway. This is because "current project" does not exist until you are in one. On a dashboard, or a search and all the other places that are not explicitly part of a project (i.e. a single issue or the project screens) you don't know what the current project is, because it could be…
-
This is a cxf question, not one for Atlassain. The message is clear - cxf as you're using it does not support RPC/SOAP. My limited understanding is that cxf can be made to do so, but you have to explicitly tell it that you're doing so. See http://cxf.apache.org/docs/developing-a-service.html
-
Yes, you've answered your own question. Independent projects don't have issue type schemes. To create a standard project, an administrator has to use the original "create project" option, and select one of the templates or shared config.
-
Change the permission schemes, removing anything that grants "delete" to non-administrators. I'd recommend doing that in all cases, not just yours - this forum is filled with people who are trying to "get back" issues that they have allowed to be destroyed, and the process is not simple.
-
Run a filter for "assignee in team" (we don't know how you are defining a team, so there's no way we can give you JQL for it). Save it, and then use the saved filter in a "filter statistics" gadget that groups by project. That will give you a list of projects that the team has assigned issues in.
-
What "web link" are you trying to create?
-
What is the full error that is given at the point it fails?
-
What does "it's not working" mean? What are the symptoms, what are you getting and what do you expect?
-
Not quite. Installation and purchase are different things. If you install Jira Software, then yes, you have core because Software needs to run on top of it. You can buy licences for Core and licences for Software. If you grant a user Core access, they'll be able to use all the Core functions. If you grant a Software…
-
They're totally different things. This comparison would be like asking what the difference between tea and a teapot. The REST API is an interface that allows software to talk to Jira. The JRJC is software that talks to Jira over the REST interface.
-
I am sorry, but no. If you delete someone, there's no records to hang on to, other than they amended stuff (and that is showing that an unkown user did it, because you no longer have any information for them)
-
Could you show us exactly what your setenv file says?
-
Not directly, as it's not quite the right thing to do. Story points should be added to a story as your team estimates them. Whilst modifying them before they go into a sprint is fine, changing the story points once you've committed to doing them is bad practice as it stops you being able to report on what you've achieved…
-
You don't need to upgrade Core, unless the new version has new/changed features that you want, or fixes for problems you need fixed. Atlassian release quite frequently - far more often than most people would like to upgrade. As an example, the people I work for offer a "managed service" - we run Atlassian stuff for you on…
-
Don't go! I quite enjoy rants! Ok, mostly the ones I tend to agree with, admittedly, or the ones where people "give themselves enough rope to hang themselves with". But most (and probably all) of what you've said about the UI for Atlassian Cloud falls firmly into "I agree". So I'll miss you if you do go.
-
Jira doesn't have anything that would do that, so it must be one of your humans who has "manage sprint" permissions.
-
Look a little above the fields you've shown in the screenshot. There is a menu bar with edit/comment/more, and then to the right, buttons that trigger "transitions" which change the status. (A drag and drop on a board is just triggering a transition in the background)
-
Have a run through the "getting started with <app>" docs on the Atlassian web site.
-
No, you can either see an issue or you can't. It's not possible (or useful to be honest) to restrict people to seeing parts of it depending on whether they're on a board or view.
-
You don't need to do this. Jira Software is an Application that runs on the Jira Platform. The Jira Platform is "Core". So if you're running Software, you already have Core, because you have to have Core to run Software on! Core handles a lot of the structure automatically, including providing the database access for…
-
Have a read of the original answer above - the last two paragraphs answer you.
-
You can get the source if you have a commercial licence. But ripping that key structure out and replacing it is * Totally unsupportable * A huge task * Need to be re-done on every upgrade * Going to mean apps, add-ons and integrations will simply not work (as they would need to be re-written too)
-
Ok, I was sort of expecting the status one to fail, not both. Try "Done".equals(it.getStatus().getName()) That's the raw Java of what you're doing that explicitly gets and tests strings. I think you'd do the same for summary but with "contains" rather than "equals"
-
I've always built off the issue history to be honest, using "status was X, changed to Y" read out of the change history. But yes, with code, not JQL.
-
Yes, that's correct. There's no way for Jira to know that two transitions should be considered the same, that would stop us from having editable workflows completely. So you'll need to deal with it either in your code or configuration (I'm guessing you're using scripted or calculated fields to capture it), or by using a…
-
https://docs.atlassian.com/jira-software/REST/7.0.4/#agile/1.0/board will get you the boards. You'll need to think about what you mean by "associated members" and work out a way to "get" them separately.
-
Transition IDs are locally unique, and nothing to do with the status or steps they move you between. If you create a workflow via project creation, you'll find each workflow has the same id for the transitions. But if you create the workflow by hand, even if it's identical, you will find the transitions have different ids,…
-
Ok, but have a look at the issue history - that should be capturing the change and who did it.
-
The formula won't give you an error itself, as the code looks ok. But I suspect the issue.get in line 1 is failing, not returning a null, and hence it never evaluates it and then moves on to the next line where it promptly fails as well. If you don't want it to run in certain projects, change the scripted field context so…
-
No, Jira ignores them in the backlog because they are not a lot of use. You can't rank them (as it's nonsense), so Jira simplifies by showing you only the issues you can rank.