Comments
-
Ok, that's really good information - the line you've got in the log file is exactly where we need to look because somewhere near there, there is a root-cause, but we need to expand on it. Could you post the rest of the stuff below that line in your log? At least as far as the next "healthy" line. We need to work through…
-
What is the "multiple assignees" field? Is it a multi-user picker? What is trying to set the field? Are you entering things on screen, or is there scripting involved? What does the log file say? What validators do you have on the transition(s)?
-
There's not a lot we can tell you about "front end is just a form". What does that mean? What is serving that up? Where is it available? Where does the bosses shortcut actually go?
-
The JDBC driver would be for reading just the data. Whatever the front-end is, it's a totally different story. If it's a web-service, you could use an iFrame, or write some Confluence code to pull it in. Or you could try to replicate some of it by using Confluence add-ons that can read via JDBC and configure them to look…
-
It's perfectly valid to say A is not linked to C because you haven't added a link to do that. The "workaround" is to create the link from A to C to tell JIRA that there is one. For reporting, everything Nicolas said is spot on!
-
Look in general configuration for the "base url" - you should change that to the ip address of your machine. I'd put all the files you've changed back the way you found them too...
-
Ok, I think what's happening is that you have set up an automation rule that is tied to the request and it's trying to do something clever. But the project and/or desk has been reconfigured and invalidated what it's trying to do.
-
Does the log show any errors at the time it throws this error?
-
There is a good write up of this at https://answers.atlassian.com/questions/128125/import-export-of-projects-from-other-ondemand-instances
-
Three steps: Log into your my.Atlassian account, the one used to purchase the system. Make sure you have other people named as the billing and technical contacts for it. Log into JIRA and go to manage users. Make sure the new admins are in the same admin groups you are When you leave, get the new administrators to remove…
-
Click Portfolio -> Create Plan
-
Please read the relevant release notes, I'm not going to waste our time by copying and pasting them here.
-
Er, your question says you are using JIRA 7.1 and you want to upgrade it to 7.1. There's no changes between those two versions. However, you can find lists of changes for all versions under https://confluence.atlassian.com/jiracore/jira-core-release-notes-781386726.html
-
You have to be an admin to create projects, and admins can access everything. So no. You can't do this level of restriction. (I've done it with addons in the past, but you can't add them to Cloud)
-
I'm not an export at SQL, just know the basics, and you're probably better off understanding the data instead of just having some SQL that does it from one angle (such as the below, where I've started from the actual change of status record. But you might want to approach it from an issue view) Read changeitem for lines…
-
No, you need a plugin for that - either a scripting plugin or one of the plugins that contains an "increment custom field" function.
-
You can create a number field and use "add to custom field" type post functions. It's also possible to create scripted/derived fields to extract it from the history, and there are some addons in the marketplace that implement those counters.
-
A lot of that is a bit too vague to answer directly. Frankly, your best bet is to simply try it for question 1. Evaluations are available for both Cloud and Server (run it yourself). If you just want a simple look around, try jira.atlassian.com for a brief introduction. The answers to questions 2 through 5 are "yes, you…
-
Ok, then you don't want sub tasks at all really. You just need a multi-check box field that has your to-do items in it, and a validator that prevents progress on the issue unless all items are ticked.
-
You could also create a really simple workflow for just the sub-tasks, with just "open" and "closed". Open would mean "unchecked" and Closed would match "checked".
-
Go to Admin -> Roles, where you can maintain the list of roles.
-
It's happening because you're deleting groups from the rights you need to grant them. Keep it simple - have a group that is clearly named for system-admins and put that in the system-admin global permission. Then make sure all the correct users are in it. As you are using external management, I'd strongly recommend having…
-
Click "edit" and put data in them. JIRA hides fields from the issue view if they are empty.
-
Yes, a JQL function is another excellent solution, I should have thought of that.
-
I've done something similar for a totally different reason. As you say, you create a multi-user-picker field, and don't put it on any view screens (it still needs to have the right context for the project and not be hidden in the field context). You then find/write a listener that picks up changes on the fields and…
-
You'll need to read the workflow to find that out - it'll need code if you want a display in JIRA.
-
I'd try "issuekey in (fa-1234, cs1k-321, avd-129)" and so-on
-
I help out with a lot of systems, and there's a pattern - a lot have zero or a tiny handful (less than 5). Then there's a bit of a gap - very few systems have between 6 and 20, but a good number have a lot more than 20. I think the largest I've seen was 200, but part of my job there was "housekeeping", and I was able to…
-
Should be able to say something like and summary !~ "end of employment" I'm not too impressed by the fuzzy searches JIRA does with sentences (it's fine with single words), so I'd check that logic without the ! to see that it includes them correctly.
-
Ah, that's not quite what you said - I was unclear on whether you meant "the file to be attached by the user" and "the file already attached to the issue". You actually need both! You've also got two separate processes to do So, you do the validation first. Your code will need to * Look at the mutable issue passed to the…