Comments
-
We're stuck at the moment. You can imagine you're not the first to hit this rather significant failure for existing users. It's logged at https://jira.atlassian.com/browse/JRA-28577 and probably better discussed there, as a way to encourage Atlassian to fix it.
-
Yup, been a bit of a pain to remember to put conditions on every new transition for the last <mumble> years.
-
Yes, it's a bit of a flaw that is fixed by Atlassian adding a default "must have a generic transition-issue permission" explicit in the permission schemes - but you'll need JIRA 6.2 or above, if I remember right. Otherwise, no, there's no protection, and anyone can use a transition unless you put at least one "condition"…
-
That article could do with some updates - there's a new add-on that can help with synchronisations, the info about Script Runner is out of date (it's supported now, and yes, I work for Adaptavist) and so-on. The basic ideas are still right of course.
-
Because you need to put conditions on workflow transitions. It's valid to have none, sometimes you do want anonymous users to be able to do things. It's really a useful thing to have even more complex globalised attitudes, it's simply not needed - the system already supports what is being asked for and making…
-
I think I saw it when it was created, and I think Atlassian closed it as "won't fix", because the conditions already exist.
-
You've set this field to be a number, but telephone numbers are not really numbers, they are effectively strings, and trying to place them into number fields won't work for the longer ones because the nnumbers fields can only hold floating point numbers up to a maximum size. I'd add a new telephone number field of type…
-
Start at https://www.atlassian.com/enterprise/data-center
-
Yes, like I said already - you run an import. The xml is not suitable for creating a database from, it needs to be imported via something that understands it.
-
Well, that's the thing, to fix it with those files, you need to run an import. The log implies you've got a broken custom field of some sort. It would be very unusual for a system field to break quite like that, so I'd look at the custom fields you have added via plugins - do you have any of these?
-
What does the log file say is going wrong with the import/upgrade?
-
Yes, you can.
-
Set up a single dummy account and set the mail handler to assume that user when it can't recognise an actual one. That dummy user will need "create issue" rights at the very least.
-
We can't. You need to talk to Atlassian's OnDemand support. We're a community of end-users, not support.
-
Yes, one very good piece of advice I learned many years ago - never have more than 10 Jira administrators (for a VERY large install) and make sure they all work together closely!
-
None yet - Jira doesn't track most admin changes (you can plough through access logs in some cases, but they won't necessarily give you any details.) There's a plugin which tracks admin changes, and I understand Atlassian are looking at some logging of admin changes too. But there's nothing in 6.1 or below natively.
-
Yes, it's the best way, and you won't do any harm. Even if you get it wrong, you will be able to remove it again later. The only caveat there is that if you remove a workflow status, then any issues that are currently in that status will need to be migrated to another (Jira will ask you what to do with them when you swap…
-
Yes, it's the best way, and you won't do any harm. Even if you get it wrong, you will be able to remove it again later. The only caveat there is that if you remove a workflow status, then any issues that are currently in that status will need to be migrated to another (Jira will ask you what to do with them when you swap…
-
Yes, it's the best way, and you won't do any harm. Even if you get it wrong, you will be able to remove it again later. The only caveat there is that if you remove a workflow status, then any issues that are currently in that status will need to be migrated to another (Jira will ask you what to do with them when you swap…
-
Issue navigator - search for the issues you have associated with the customer, then you have a basic grid-like result with several options for export (excel etc). Save the filter and you can push it through gadgets and other reports. I don't think you can get to a really basic key/summary and nothing else report, but you…
-
Why you can't find them though, I don't know. I personally don't like the structure of the docs for JIRA 7, I can't find a lot of stuff either. I think a lot of it hasn't really been written yet, but I'm still mostly using the docs for 6.
-
Short version: https://confluence.atlassian.com/agile/glossary/epic Longer version: https://www.atlassian.com/agile/delivery-vehicles/ Working with them in JIRA Software: https://confluence.atlassian.com/agile/jira-agile-user-s-guide/working-with-epics
-
They probably just need "browse user" global permission.
-
Um, so add a user who can look at user profiles. Not sure what the question is here.
-
What is the integration between JSD and Office you are trying to do?
-
No, because it's not a number. An older version used to use a number as the rank, but it became unwieldy and slow because as usage grows, you have to start updating swathes of issues to make space for updates. It's using a "lexorank" system now, which can't really be translated into numbers.
-
What did you restore? Where to? What does the log file say?
-
The charting only adds a handful more, but they're often useful. I'm not sure why they haven't just been absorbed. I don't think I've ever found a site where the Calendar isn't useful to anyone!
-
Close.First, always* Toolkit* Suite Utilities* CalendarThen I look at * Charting* Script RunnerI caveat the Script Runner though - because it effectively opens up the internals of JIRA, your admins need to be at least aware that they could make a mess and hence be careful (and I've done a lot of cleaning up of data damaged…
-
Absolutely, I'd always look at the size of a vendor as part of the evaluation process.I still owe Jamie a lot of beer for the script-runner. I'm hoping to be able to spend more time with him when the current project finishes, so far, it's been the Christmas party and one afternoon when I popped into the office.