Comments
-
What do you mean by "case study slider"? What are you looking for here? A job description? Training? An idea of what a Jira admin does all day?
-
Not directly. At present, you would have to buy the new Cloud url, export from the old one and import into the new one, then shut down the old. Not technically a rename. There is an issue open with Atlassian to get this fixed
-
Check what the permission scheme says. Hopefully, as recommended, it will say "Project Admin: Role (something)" Go to project admin -> people/user and add the user to the named role. If you have other permission rules, it gets more complex.
-
You would need to download the source code of Jira, find the modules that render the issue view, amend them so that they understand they need to move your field, recompile (at least that module) and redeploy You'll be unsupported, and have to repeat this on every upgrade. I cannot recommend doing it.
-
I've not looked into the code for Jira for a while, and I can't remember exactly.
-
Make them project lead (you don't have to give project lead any admin), then tell it to assign to project lead. Or make them a component lead on all components and make component mandatory so the user must fill in at least one. As mentioned above, whack in a post-function on issue-create that assigns it to that person.…
-
Rather than a local mirror, have you considered just moving to Server?
-
That suggests that one of your admins has made the resolution field mandatory in the field configuration scheme. This is something they should never do - you'll need to find them and get them to fix their mistake. (Well, ok, there are some edge cases in making project behave very strangely, but this is not the place for…
-
There's no way to do this, without writing your own "move" code, or hacking the existing one. The move permission allows a user to move an issue out of a project, but has no further conditions or anywhere to add them. (and they need create permission in the target project). It doesn't care what the data is, until it does…
-
And I need a pet thermonuclear warhead. Please have a read of the conversations above, a statement of "I want" is pointless in the face of evidence.
-
It usually means there is no story point data yet.
-
Your screenshot implies there were (sub-)tasks you can't see, because it does not list the 1-4 parent issues they were on. I'm not sure what "I had to remove the subtask from the sprint" means, as you can't move subtasks out of sprints.
-
JQL finds issues, not the data from them. This leads me into the next question, in that I don't know how you are defining "service" or "time spent without service", or "if status stays tuned". Could you give a bit more context to your question? Define what a service is, explain the process and expectation. (Time spent will…
-
What do the application and server logs say? ( <jira home>/logs/atlassian-jira.log and <jira install>/log/catalina.out) Did you forget to set a jira home in the properties file?
-
In theory, yes, but I don't think they do it in practice. Raise a support request at https://support.atlassian.com/contact and see what the response is.
-
Ok, so you've got it started at least. Try re-indexing next!
-
My best guess is that you are on Cloud Confluence?
-
No time component means what it says. There's no time in a due date. You can say something is due on Monday, but not when on Monday, because there's no time there. What time of day is it if I say just "12th January 2019"? Your new requirement is possible though, ignoring the time - due < endOfWeek() due > endOfWeek() and…
-
The only way to do this would be to make changes to the issues, forcing them into a "frozen" status, with all the complexity of then moving them back, or botching the permission scheme, flipping the update flags on and off (which could affect many projects). This is a very very complex and risky thing to do to your system,…
-
A due date is just a date, it has no time component. You'll need to use a different field - a custom field of type date/time.
-
Start with a look through https://confluence.atlassian.com/jirakb/jira-fails-to-start-due-to-multiple-entries-with-same-key-800702874.html
-
No, that defeats the whole purpose of sprints with subtasks. The point of a sprint is you commit to doing a set of stories. If you break up a story into sub-tasks to help you manage it, allocate different bits out, differentiate between types of work, or teams, and so-on, that's fine. But a story, by definition, cannot be…
-
What message is it giving you to tell you that you cannot close it?
-
Start at https://confluence.atlassian.com/jirasoftware/jira-software-7-0-x-release-notes-776997721.html and go over the release notes you need to see.
-
We'll need a bit more context - people often use "combo box" to mean different types of field (none of which make sense in html or Jira speak), and Web Sharepoint is totally out of context for us!
-
They are generated at run time and cached, usually in the directory Matt points to.
-
Your database is misconfigured. This isn't quite the same error, but it's the same root-cause: https://confluence.atlassian.com/jirakb/jira-cannot-create-issues-when-using-mysql-with-binary-logging-292651355.html
-
You're fine - your licence covers you for any version released before it expires. If Atlassian release version 8.0 in September this year, you'll be able to upgrade to that (at no cost, other than performing the upgrade and training users)
-
"None" means "empty". Empty is what the "mandatory" flag is there to prevent. You can't set a mandatory field to "none" because that is what mandatory does NOT mean. To allow your users to select "none", make the field optional. If you mean you want to force your users to change a value, then you'll need a validator to…
-
Resolution. If the resolution field is empty, the issue is "not done", and drawn normally. If any resolution is set, it's resolved and hence struck out.