Comments
-
I am sorry, but that does not make sense. Your first question doesn't say where the "allow selection" is happening, what field configuration has to do with it, or where "it is not going to apply" applies. I've tried to take a guess, but I can't work out what you're talking about, there's not enough information. Your second…
-
If you're using hosting services, then you'll need to ask the hosts for the logs. If they're hiding them from you (I know many, including Atlassian Cloud, do, for the sake of simplicity), then they're implicitly taking responsibility if something goes wrong and needs debugging via logs.
-
Can you check the "workflow properties" on the status the issues are in? You'll have to draft the workflow (but you can just stop and not publish the draft) to get to it. I suspect you'll find it's got "jira.issue.editable = false" on it.
-
On the main menu, issues -> search
-
Everyone uses it on a url. You need to go on to the server, find the log file and tell us what it says when the upload fails.
-
I don't really know how else to say this. We need to see the log files. When you get errors like this, they are also writing errors into the log files. We need to see the erros in the logs. Not the errors on screen. Not a repeat of what you've already done. The log. Show us what the log file says.
-
Yes, sorry, I should have been more clear. We need the full error messages.
-
With a listener - they're for picking up and responding to events.
-
What do the log files say is going wrong?
-
It's not a "create" though. The issue already exists, it's got content and a history. What you need to do is trap the "move" event and replicate the post-functions in a listener.
-
The add-on was written when JIRA did not allow any duplicate names. Atlassian removed that a while ago, but are under pressure to put it back, as it's a total nightmare having fields of the same name. Try renaming the "type" custom field, that should tell you if you have the wrong field on screen and in the validator.
-
That appears to be the name you have put on the account. There's two steps to check. First, search your user lists for that email address. Any user using it should be named with the name you want to see. Second, you should look in your email address book, as you'll need to change the name there too, or some email clients…
-
Not in JIRA, as JIRA isn't really for that. But it is in JIRA Service Desk. It's not what I think you are really talking about, but JSD has "Automation" that can do this sort of thing. There's a rule for Automation that shows as "Keep on top of SLAs" - that should enable you to set up a form of escalation. Have a look at…
-
I am assuming that you are using a validator that checks a field has a value, and not one that checks that the data has changed during the current transition? That may affect how we solve this problem, but the core of the problem is the same - you've demanded a field from a user but not given them the chance to enter it.…
-
Ah, no, it's not quite. That's almost a stub add-on. JIRA Software is an application. You need to look at the Application you have installed, and check the application access.
-
The button was renamed "Boards" in JIRA 7.0. Cloud is on roughly 7.3, and if you don't have that button, you need to check that you have access to "JIRA Software"
-
Ok, could you explain what it is adding up and what you think it should be adding up? Might be easiest to show us a filter for "Sprint = Sprint 27" and show us the issue keys, story points, status and resolution ?
-
Not at a project level, unless you install an add-on to provide such a field. You could just put their name in the project description field though.
-
Read it - log in as an admin and edit it. Non-admin users can get a workflow diagram if they have "view workflow" permission and they look at the issue in the standard issue view. They will be able to see if there is a transition there at least, but won't be told if there are conditions like "assignee only"
-
It means you're running JIRA on a server and you're connected to it by running a browser on that server.
-
I'm afraid this approach simply won't work. Take a step back and think it through: You have an issue which represents a real-life thing that needs doing (e.g. "Build a new penguin pool"). That will naturally break down into "Conception - designing a pool", "Execution - building a pool" and "Search - finding some penguins".…
-
That is correct, you have an issue without a fix version. Does the re-index affect the "is empty" question?
-
Hmm. Could you show us the header of the next sprint? What does it look like in planning before you close the current sprint? Also, do you have parallel sprints enabled?
-
You still need the permission to attach files in the project.
-
JIRA Service Desk and JIRA Software are applications that run inside a JIRA Core installation. If you've installed either of these, you have Core running already. From what you've said here, I suspect you're installed Core over the top of an existing Software/SD, which would have removed them. Can you check under Admin ->…
-
A velocity report is generated by the boards you're working on, so you need to go to the boards to get there. But, it's not really calcuable with any accuracy until you've done a few sprints - from memory, you'll need to complete three sprints before it will give you full details.
-
Ah, good, that's the right way to approach it. The problem you have is that your script is not pushing the right type of data into the label field. A string field is a string of letters. A label field is a collection of individual labels, each of which holds a string that is the name of the label. In your code, the…
-
Add-ons for Atlassian stuff have to match the licences for the application they are being installed into. So, if your Bitbucket is a 2,000 user licence server, you will need to buy the add-on for 2,000 people, even if your team is only 10 people.
-
You can't just change a field from one type to another. Do you mean you have a label field that you are trying to copy some text into from another field?
-
It is correct. Deleting issues means deleting them, and once you've done it, the only place to get them back from is a backup. The mistake you've made here is thinking that issues belong to boards - they do not. A board is a view of a set of issues. You could have hundreds of boards looking at an issue, but there's only…