Comments
-
That's what the documentation tells you to do in the application link section, yes. Triggers will have to be defined separately, but will refer to the application link.
-
Ok, forget Fisheye as you're not using it and don't need it. You have Bitbucket. What url do you use to connect to that in your browser or IDE?
-
You use the url that you use to connect to the server you are trying to connect to.Seriously, WHERE is your Fisheye server? How do you get to it in a browser?
-
I repeat: How do you connect to Fisheye in your browser? What url do you put in there?
-
I don't know how I can say this any other way, but I'll try.You say you want to link to Fisheye. You need the url for Fisheye. How do you connect to Fisheye in your browser? What url do you put in there?
-
You've updated the question, but not told us any more. To link applications, you give the systems the urls of the systems you want to link to.
-
The links are the urls of the applications you are asking about. I think the question is a little unclear, I'm not entirely sure what you are looking for here?
-
Virtually identical question asked earlier today - see https://answers.atlassian.com/questions/279543/set-permission-ondemand
-
But where did you add the user?
-
Sounds like you've added them to a different user directory (the internal one?), so it's not using LDAP for their account, and hence, not picking up the right groups etc.
-
Yes. That's one of the things the dashboards are for! A lot of gadgets work off filters, so you just need to create saved filters to drive the dashboard, and you can do things like "project in (xxx, yyy, zzz)" in filters.
-
You'll need to find or write some code that can read your AD for that information and use it in the relevant place in the workflow.
-
Sounds like the user you are running this as does not have permissions to assign issues That's from your first line. The exception you're getting actually tells us that your user doesn't have rights to view either. So I think you need to work on the user login and permissions...
-
You might want to comment, watch and vote for https://jira.atlassian.com/browse/JRA-9367- the request to make the "apparently random fields vanishing" actually make sense to the end-user.
-
Ok, so you have three fields. I'd recommend renaming one of the Severity fields to something slightly different so that you can tell Also, I really do mean what *type* of fields they are. When you added them, exactly what type of custom field did you use? And is priority the built-in system priority or another cystom field?
-
What does "field name called severity has 2 fields" mean? A field is a field. Do you mean your severity is a custom field of type "cascading select"? Could you tell us what types of field both priority and severity are? (I'd try Andris's fix first though)
-
Yes, that's right.
-
The system must use a user type field for this sort of thing, there's no other way to usefully identify a user object. Try this: * Add a user-picker field * Set the permission scheme to say "Assignee = <user picker field>" (alongside other rules) * Find (or create) a user who is NOT normally an assignable user in that…
-
You'll need to create a new field configuration and set the field optional in it. Then create a new field configuration scheme and tell it to use the new field configuration. Then go to the project admin and choose the new scheme. (Note - the first two steps are often easier if you copy the existing stuff and amend it)
-
Ok, you'll need to read the application logs for more detail. This is actually a Tomcat error, but it's something to do with JIRA not giving it information it needs. Check out <JIRA home>/logs/atlassian-jira.log and <JIRA install>/log/catalina.out
-
I'm not clear on what "display a project's page" means. Are you simply clicking on a menu option? If so, then which one? If it's not part of the main UI and you're talking about add-ons or coding, could you explain what that is in a bit more detail?
-
No, if you set it to email the assignee, it will send it to the assignee. You can't arbitrarily turn it off for random users.
-
Maybe. It depends. What do you mean by "custom" - are you talking about the list of users you are sending to, or the actual content of the email? In both cases, how are you making the decision on what to send to whom?
-
For Agile, you need to make sure you have JIRA Software, not just JIRA Core. For Tempo, you need to add the Tempo add-on in your account.
-
I don't think your REST JQL is incorrect, I suspect it's that you are logging in as a user who doesn't have permission to see the project.
-
That does not matter. If you delete the field, there is nothing in the field configuration for it, because there's no field. Even if it hangs over in the database (which it does not), it doesn't do anything because the field has gone. You have a function using it somewhere.
-
Er, that doesn't happen. If you delete a field, it's gone. It can't be marked mandatory in the field config because it's not there. There's nothing to check.
-
Doesn't always work though - it depends on the whether the damaged transition is still coherent enough to be referenced by the editor.
-
Bother, I was afraid of that - Jira can't display the broken post-functions (and hence the options to edit/delete them). You've got two options: 1. Create a new workflow and migrate the project over to use it 2. (This one is risky and really desperately needs you to take a solid database backup before you try it). Add a…
-
Oh, yuck, I hate it when I do that. The short answer is to manually edit the workflow and look at the create transition, removing any offending post-functions. It might also be happening in a listener, so you'll need to check those as well if you've configured any. One quick cheat for workflows - if you download a suspect…