Comments
-
Hover the cursor to the right hand side of a post, on the first line. A ... menu should appear, it contains "edit"
-
So the ? user is in the role CR Users in the project via an invidual role or a group in the role, and/or in the group Tool_Jira_localuser
-
The burndown chart you would look like that if you had been moving the stories to "done" during the sprint. You've moved them all at the end of the sprint and you've been adding points into the sprint during the execution. The graph can only go on the information you give it.
-
Please explain "get" and which API you want (REST or internal).
-
No, because the main point of watching is that you get emailed on changes.
-
Did the same thing happen with another browser? And language selection?
-
Is this a standard "blank page" you are creating, or is it from a template? Can you try a different browser and check that you have the same problem?
-
Is the "done" status in the UAT column then?
-
Definitely. I usually use a Jira support project to log requests and updates in.
-
I'm not sure what's wrong with it, could you explain? It now has the line falling on the far right, as you've marked some stuff "done", so it looks right to me.
-
Yes. CSV import is "one issue per line"
-
It's the only one I've run into that enables you to pretend there are heirarchies like sub-projects. Most Jira users don't use sub-projects though, and when they need project planning, reach for Portfolio or Big Picture. Structure is good at what it does, but I've seen it all-to-often abused - people building complex…
-
You have written a script that is trying to insert rubbish into a multi-select field. It needs to pass in a list of options, not a pile of text.
-
Almworks are working on Structure for Cloud, I understand it's in Beta already. I'm sure they'll be able to tell you more!
-
Pretty much. There is still a Core of Jira there, with the projects, issues, workflows and fields, but a lot of the rest of it is diverging. You should make your choices based on scale and functionality - Cloud doesn't go above 2,000 users and 100Gb storage (there's talk of that going higher, but not any time soon). Server…
-
It used to be weeks when Cloud was being seen as the lead, but as Cloud and Server are diverging, there's no answer any more. Some features appear on Cloud and can take anything from a week to years to go to server. Some features no longer go across at all (business boards have been on Cloud for well over a year for…
-
It looks like someone has tried to put html into a translation. Could you confirm this by trying another browser, and also swapping to a different language in your profile (just check the other language has the tags as well, then flip back)
-
Yes, but keep a lid on them - reuse them where possible and keep the names generic to enable re-use (e.g. if they ask for "Process XYZ Start Date", don't do it. Just say "Start Date", and you'll be able to use that field in other places when someone asks for a date field for something else). Don't let the users do silly…
-
You can't change the name of personal spaces. They show the name of the user it belongs to.
-
That's a valid user who is included in the projects "can be assigned issues" permission. That probably says "role: developers" - remove that user from the role and it will go away.
-
Is "done" in the rightmost column on the scrum board?
-
Go to the Jira Admin section and look for "application access". That will tell you the groups named for access to Jira. Also check the "global permissions" for groups named as System and Jira administrators. You have 11 or more different people named in those groups combined.
-
Take a step back. Issue security is for hiding issues within projects. You need to hide entire projects, so you should be doing this in the project permission scheme. Look specifically at the "browse" permission, it is likely to say "Browse: role User". Go into the project's "people" section and look at who is in the role…
-
If there are errors in the import, it's because you are importing something that's broken. Making even more mess in the database is just going to make it worse (The fact you think there's only one table to update shows that you don't know enough to even start amending the database) Please, use the UI to manage your…
-
Better to do that with a custom field, than hack the database.
-
Wrong, a migration will keep the same workflow, with all the conditions, validators and post-functions. I suspect you are actually talking about something different - could you explain what you are doing?
-
No. There's no "solution" because the created date is supposed to be when the issue was entered. Botching it is not the right thing to do. If you are suggesting changing it to reflect when something happened rather than creating the issue, that's fine - create a date/time custom field to capture that.
-
This is usually caused by running it as the wrong user, then restarting it as the right one. When run as the wrong user, that user takes ownership of some of the files, rendering the correct user unable to read/write them. Stop the system, correct the ownership and restart it as the right user.
-
Ok, so you really do not understand the database well enough to even look at the SQL (you're not alone, it's not a simple database) If you need to update the workflow, then edit it in the UI. There is a draft mode that lets you change most of it.
-
I don't understand the question. If you are on Cloud, you can not set the server base url