Comments
-
Check the permission scheme - you should be able to limit the possible assignees to just the people you need by modifying the permissions and role memberships.
-
Excellent, that covers almost every scenario I was worried about.
-
Quite a lot of people are going to find it impossible to upgrade at all, they need flexible keys.
-
Thanks for going back over the docs to clarify it - I was working from memory! I first ran into this when someone wanted to use a - in a Jira 3.something project (Not sure of the exact version, but it was between 3.0.3 and 3.3.1). Jira coped with it ok, but a couple of the plugins were assuming that the "-" was the…
-
Yup. I've seen it documented several times, but it was always quite well buried (in an appropriate and relevant place, but you always had to dig to find it), and never highlighted as a "standard", just the off-the-shelf default. I was highlighting the point that even if you could consider it a standard, it's one that has…
-
The "standard" for version 2 and 3 was a key of 2 or more letters, with an upper limit high enough that you don't really care (I don't know what it was, but I never hit it) In version 5, they chopped the maximum to 10 characters, which is too short. In version 6, it looks like we won't be able to deviate from 2-10 letters,…
-
It's a bad decision in its current format. I would completely understand a decision to stop supporting project keys with "odd" characaters in them, but unless full support for alphanumeric keys is implemented, this is going to stop people using Jira. Numerics are a critical part of some projects codes because people embed…
-
Where are your groups stored? Internal directory or external (like leap)? Are the groups you want to add available in other places (ideally, check a permission scheme - edit one, start to add a new group to a browse permission. No need to add it, just check the list of groups is complete). Finally, are you in the group you…
-
Could you check a couple of things for us? First, can you confirm that your url has not changed? (If you trial on one url, but buy another, they're separate instances) Second, what groups is your account in? Third, could you go to "manage applications" and check that you have JIRA Software in there, and what groups are…
-
All edit type screens put the comment option in front of the user, if the user has "comment on issue" permission. It's useful for most cases - I often find "fixed" is too short a description for how I resolved an issue. I think you could disable the permission on that transition by using workflow properties on it, but I'm…
-
If you're worried about users creating duplicate content, then the obvious answer is that you should un-hide the stuff they're duplicating. I don't think there's any sense or value in telling people "hey, there's a space over there for that... but we're not going to let you see it". But, if you must do this, you're going…
-
Ok, there is no "project roles" box on the screens you should be using, so I need some precision. When you go to the project and then into the project roles screen, go to the row "users" and then the second column. If you go to the end of the list (if there are already groups in there), what happens when you type…
-
When you go to the project, and then into the roles, can you add the groups in there? Even without any lookup? Let's say you added a group called "penguins". Can you go to the roles in your project, type "penguins" into the row of users in the column groups and save it?
-
Yes, this is not an uncommon complaint. Start with a look at https://confluence.atlassian.com/display/CLOUDKB/JIRA+or+Confluence+Cloud+Instance+is+Running+Slowly and see if there is anything in there that can improve it.
-
Ok, you'll need some form of escalation script for this. Most of the approaches use the same filter idea I gave you above, but with escalation, you should transition or comment on the issue (both of those can fire an event you can use in the notification scheme and send to "assignee")
-
We'll need more detail for a thorough answer, but to get started with. Create a filter that searches for the issues you want (e.g. "unresolved and due date in the next 7 days"), save it, and subscribe to it. It will email you regularly with the list.
-
I don't think you can do this in OnDemand. I've been doing it for years using "jelly escalation", but OnDemand doesn't support Jelly scripting or services (yet) The best you can do is create a filter for "issues past due" and then use a subscription to get it regularly. It's a list, generated at the time the subscrition is…
-
Possibly, but you need to tell us what you actually want before we can help you much
-
It puts its logging into the application log, with everything else. You'll want to read atlassian-jira.log
-
It's a bit ugly, but you could allow "unassigned" and use another field to point at a dummy user (you'd need to beat it into... sorry, "educate" your users that unassigned = with a dummy user though, and think about emails if you need them to go out to the dummies)
-
Well, actually, JIRA Service Desk is a bit different - you can have unlimited numbers of "customers", but you don't assign issues to them so they don't need a full JIRA account - the Service Desk handles the current "ownership" of an issue.If you don't have Service Desk, then you need an account with a licence to be…
-
Your third link is a good one to start with, but I also find https://confluence.atlassian.com/jira/integrating-jira-with-iis-185729648.html very useful (skim it until you reach section 4) Generally, you'll find it easiest to get it working without SSL first, then add it later. SSL is a pain to configure, but if you can…
-
Jira is an issue tracker, not a wiki. It's got some basic text formatting in some it's fields, but everything belongs to issues. You might want to take a look at Confluence, which is the Wiki software Atlassian does - it integrates well with Jira (more tightly with every release) and is available to OnDemand users…
-
Don't worry about the "resource not found" error, that's a symptom of the core problem that you're struggling with the data restoration. Basically Jira cannot start. You haven't attached a screenshot, but when we're looking at system errors at this level, they don't tend to be that helpful - it's quicker, neater and more…
-
When it's ready. Atlassian don't commit to release dates because it's a dumb idea to release software until you're 100% sure it's ready. See https://answers.atlassian.com/questions/24671/target-release-dates-for-jira-5-0-and-gh-5-8 for a bit more discussion, and a comment along the lines of "Early in 2012"
-
I'd give the Zephyr for JIRA Importer a try first
-
We don't know. You have not explained how you are representing test cases in JIRA.
-
Depends on how you want to represent them in JIRA really.
-
OK, and is the user list definitely valid? And the user doing the import has "assign issue" rights?
-
Did the assignees in the target project have the "can be assigned issues" permission? If they can't be assigned, I suspect the import won't let you set them as assignee.