Comments
-
Duplicate of https://answers.atlassian.com/questions/37050537
-
Go into the project and select the ones you need.
-
You're thinking of the scheme association back to front. You don't "associate a project with a field configuration scheme", you "select the scheme you want for this project". Same as the screen and issue type schemes - there's a big pile of them that you *could* use, and you go into the project and select them.
-
You need to check THREE things. First, as Bhushan has mentioned, the more important thing is to check that the projects are both using the right "issue type screen schemes", which determine which screen (collection of fields) is in use. Second, check that the custom fields are valid for the project/issuetype you have…
-
Yes and no. There are two types of thing you can to to an issue. * An action - these update the issue in some way, but do not move it on in the process (workflow). Editing an issue, commenting on it, reassigning it, cloning, deleting, logging work, etc. These actions have nothing to do with the type of the issue, they…
-
You probably need to contact "flapps" to find out what changed.
-
But you can always go back in and share it with more emails
-
Oh you meant the email it to people, I thought you meant the permission sharing (confusingly, they both say "share"). I can add as many emails as I like in this 6.4.11 system, so I'm not sure what's happening in yours.
-
All of them. You can share with anyone.
-
First of all, a validator is absolutely the wrong place to do this. A validator is for checking input is correct, not setting data. You should be doing this in a post-function or a listener. Secondly, you can't. Jira's assignee field holds a single value. Reporter OR defect manager. Whichever "set assignee" call you are…
-
Ah, good. The reason is that I was suspecting the caches. If the second Jira were running, the caches would be out of line, but as it's offline, it's not that. I must admit I'm a little bit stuck - our DR is rigged up much the same as you've got, but the workflows seem to come across ok. As your setup is much as Atlassian…
-
That sounds like you've got two Jira installs running against two separate (but replicated) database instances. You do know that you can't do that? Only one of them can run at a time?
-
Ah, ok, that makes sense, but I don't really know much about more recent change tools - most of my recent engagements covering CRs do it in JIRA, rather than other tools.
-
A couple of times, yes, although the work tended to be bespoke customisations (get the change request tool to poke data into JIRA, or get JIRA to update it), or more a case of "moving the change control process into JIRA". What tool are you looking at?
-
Please read the conversation above - it clearly says "I only found this on Begin Work."
-
But the conversation identifies begin work as being the problem, not create.
-
Ok, it's not a post-function. Do you have any listeners in use?
-
See the previous answer starting with the screenshot with OSI at the top of it.
-
That suggests Alok is correct - you have a postfunction on "begin work" that sets it.
-
Look in the permission scheme for the permission. Sounds like the project has admin set as the lead
-
Yes, the project is configured to set the assignee to a default assignee who happens to be the admin.Assign to me should still work, assuming the users have the "can be assigned" permission (it shouldn't offer the option if they don't)
-
Log in as yourself when you are clicking "assign to me" rather than the admin. Make sure your account has "can be assigned issues" permission too.
-
Service Desk is a layer of functions over JIRA, so it uses the JIRA issue numbers. These are numerics, sequentially generated and take the format <project-key>-id. Each project starts at 1 and simply counts up.
-
Start at https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA
-
/me had bookmarked it permanently even before the re-write :-)
-
Excellent question. If I had my way, Answers would have a short, snappy list of maybe 8-ish FAQs so that those of us who answer the same question over and over and over and over could simply paste "see that" (ideally, as a single click) Your question could be converted almost verbatim into one of the top FAQs. The only…
-
Ah, the function calls in the custom field post-function add-on. No, the only functions available there are the listed ones.
-
What do you mean by macro? Automatic assignee can be done by selecting "automatic" when creating an issue. The rules are set on a project/component level
-
Oops. Make sure you add new transitions in and out of the new status/step as well, or you won't be able to use it.
-
Edit the workflow, add a new status into it and select the status you've just created. (That assumes you use the diagram view. For text view, it's "create a new step and associate it with the new status")