Comments
-
I can't work out how you've got there. It's not even something you can turn off by disabling system add-ons. If you're running 7.6, you really should be seeing priority schemes as per that document.
-
I think you'll need to read the log file for the time you get the message.
-
Don't think this is a pun, but it's a Christmas joke that made me laugh (I have to at the moment, I live in the UK, and it's either laughing at how stupid it's got, or crying): Why was the Prime Minister Theresa May sacked as nativity manager? She couldn't run a stable government. But one of my long-term go-to bad puns is:…
-
Or use sub-tasks as intended - break down the work into bits and assign the parts out. Or use a group picker to indicate a group responsible. But, always have a single person "own" the main issue by being assigned it. In real life, multiple assignees only works in two narrow conditions, and in neither of them do you…
-
You need to move the issues through a transition that sets the resolution (either with a post-function, or by having a screen with the resolution on it) A typical way to do that is to temporarily add a transition back to the current status to your workflow. You could also edit it into the issues, if you are *very* careful…
-
Have a read through Andrew's "upgrading Jira" link.
-
I'm afraid I can't tell you any more. I would say that you have not set up the Tomcat and Apache connector correctly, but you have not gone into any detail about what you've done, so I cannot tell much more than that.
-
Why don't they get the "high level reports"? What are they and how are you getting to them for PMs and developers?
-
Your best option is to let them into Jira so they can see for themselves.
-
Are you sure your upgrade worked? A 7.6 install I've got has the schemes.
-
It's under admin -> issues -> priority schemes. What do you get when you use the admin search function?
-
Search for "issue in sprint" and use the issue navigator's export functions to draw the issues out. But, you're going to find it harder to manage your tasks outside Jira than in it.
-
Jira Core is a platform, as well as a base issue tracker. Software and Service Desk are applications that can be added to that platform. You can download a Core, Software or SD installer, but, the second and third of those are only "Core with <application> pre-installed", and it's mildly annoying that there is no installer…
-
Space by space I'm afraid. A full export will replace the whole target system!
-
Check the release notes, check you have matching add-ons (if you want to keep using them), export a space, then import it. I tend to follow the Atlassian docs for the target version initially, until testing throws up problems (generally, it doesn't)
-
Not sure why you're looking at threads a decade old, but I'd recommend not bothering from now on. The current behaviour is that you set a default assignee in the project settings. This can be project lead, unassigned, or component lead (or the odd case of "project default). When you create an issue, the assignee defaults…
-
Open up the workflow again and have a look at the "conditions" on the workflow transition called "not accepted". A user needs to meet all the rules set in the conditions there (which are usually things like "must be in role X", and "must have resolve issues permission", but could be almost anything), plus they need to have…
-
The conversation you have found is saying much the same thing - you get the full functionality of the linking when using a single Jira. They're not talking about using two separate instances mostly (and when they are, it's about only getting the standard "remote link" functions)
-
Ugh, no, SQL is by far the worst possible way to attempt this. You'll be messing with 40ish tables, trying to work out their relationships and which ones need updating with data outside the stuff you're trying to import. Space export and import is a few clicks, with little margin for error, and by far the fastest and…
-
I think you would be much better off working out what has gone wrong, not "plaster over the cracks"
-
Sorry, I've completely misunderstood it. The subtask column is a single field. It displays subtasks, unfiltered. So the filter in use for the gadget is irrelevant, because the data in there is not issues being selected. You'll need to find a new "subtasks" field, one that can filter for unresolved only.
-
That's where Ivan's clause comes in. The strikethrough happens when an issue has a value in the resolution field. So "and resolution is empty" will remove those from the results.
-
There is only the Epic link. She may have been using a system where an add-on or hack provides some form of Story Link, but I'm not aware of any in the marketplace that might do it.
-
You will need to explain more than that.
-
Talk to the admins of the partner's Jira and Confluence, they should be able to add the Atlassian user account with the right email address to their system.
-
You can literally just add the two strings Ivan and I gave at the end - you have a simple set of "and"s connecting your clauses, so you don't need to think about compounding it up.
-
No, stuff moves in admin and I struggle to remember where things are in different versions. Try typing "links" into the admin search box, or use . to pop the search up.
-
There are lines in your log saying Error occurred while creating issue through workflow: Team is required. So you need to give it data for the Team field
-
Go to Admin -> Issues -> Issue links and add a new issue link type. Then you'll be able to use it when selecting "link issue" from the issue view.
-
Epic Link is a special system field added by Jira Software. There's no Story Link field, but there's nothing to stop you adding standard links (and even defining a link type for it)