Comments
-
Yes. That's a really short answer, but you've got it pretty much right there, as long as the copy of the database looks the same to Confluence, just changing the jdbc url should effectively move it.
-
Depends on how your webservice expects to be invoked. You can write code to trigger anything you want in a post-function or listener, so the question really isn't about JIRA, it's about how your external stuff is called.
-
You won't be able to "push into a table" - you cannot update data in a JIRA database while it is running (and you should avoid it when it's not running too)Again, I'd have a look at the "database fields" in the marketplace - they can use a remote database as a source of field options.
-
You'll need to find or write something that can do this. On the JIRA side, the minimal stuff you probably need is post-functions or listeners that can poke stuff into Remedy, and I'd look at the database fields for the "populate Remedy data in JIRA screen" I'd strongly recommend a look at the Connector provided over…
-
No, the setting is only used when someone tries to attach a new file (or replace an old one)
-
Yes, the default schemes are not exactly helpful when you decide you need to hide or limit access to projects.
-
You'll need to re-engineer the schemes to do this. What you need to do is * Remove the project lead from anything that sends them a notification, * Then add a role (or roles) you'll need for the next step * It's quite likely that the removal of "anything sending a notification" has removed the lead's permissions as well,…
-
You'll need to talk to OnDemand support about getting a regular copy of the backups or an xml export.
-
As per 5.x instruction, although I don't know if that is a "restricted function" on Cloud - if it is, you can try asking Atlassian support to change it, but I'm not sure if they will.
-
Start with https://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email Basically, you need a POP or IMAP mailbox for it to monitor, then emails to that address will be processed as per handler. The assignee is done outside the email part though - it'll do whatever the "default assignee" setting is…
-
I just can't see a need for an account to do this one single piece of configuration work. Your admins should do it.
-
That does not explain what the requirement is.Configuring application links is something that should only be done by proper JIRA administrators. Letting someone else configure them would be a security hole. I don't understand *why* you want to do this. Log in as yourself and configure the link. You don't need or want a…
-
No, sorry, not wanting to give admin to other people is absolutely right.What I don't understand is the requirement to change application links without logging in. Application links should change rarely and should only be updated by Administrators that understand them. Your desire to let other people do it is a massive…
-
No. They can log in. They can't change admin settings without being authenticated, so it allows loing.This does sound very much like a broken requirement. Why do you want this?
-
To be able to configure an application link, a user must have administrative rights. If you have admin rights, you can log in. So no. I'm also curious - what sort of logic gets you to this requirement? It sounds like complete nonsense to me.
-
That's the difficulty for me - I don't know what your process is, or how you want to represent issues that have a mixed set of sub-tasks! My instinct would be to keep the stories on the board, and script something that sets the "impediment flag" on a parent whenever a sub-task is transitioned into "blocked" - that way you…
-
That depends on the workflow for the Story and how you want to handle it! Story X there is clearly not in a "to do" or "done" column, but I don't know what your process for stories is, so I can't tell you where it might best land.
-
dbconfig.xml should be in the "JIRA home" directory. Check in there first.
-
Ah, i see. You are not inflicting it on the while system, just creating new schemes. As we said already, it's not screens or types to look at, it is just the field configuration. I seem to remember a function on fieldlayouitem that sets/blanks the mandatory flag in the field config, but I haven't coded in that area for ages
-
A validator will not give you the asterix. The field configuration will. To do it in the UI, go to admin -> field configurations -> Field configuration, find the field you want to make mandatory and click the mandatory flag. For each one. Programatically, er, well, don't. You almost certainly don't want to make a custom…
-
Issue create is a transition, just an odd one (no conditions, and no start point). You can add validators to create. Also, you can make a field required in the field configurations and Jira will require it on issue-create (you just won't be able to blank it out anywhere in the issue lifecycle)
-
It's a common request with an easy fix, but it's nothing to do with screens or field configurations. A screen simply says "this field shows when I am used for create/edit/view/transition". It has nothing to say about mandatory fields A field configuration is totally different. It's got nothing to say about what fields are…
-
It sounds like you have not put a screen on the transition - you need a screen there to show to the user for the comment. (The validator in the JMWE only checks the input, it doesn't add the screen for you)
-
JIRA already has that function in the issue actions (as long as your user has "move" permission) If you need that on the main screen instead of in a menu, then all you really need to do is duplicate the link on the main view - should be possible with a web-fragment or possibly some javascript.
-
Right, I think you've hit a bug there. I think it might be best to go to Atlassian with this one
-
I'm assuming you are transferring the export from the source machine to the target. Are you sure the files are identical on both machines? Could you try not using zip as well (some windows compression programs have "issues", shall we say)
-
What does the log say when you export?
-
You don't. The email handlers work on a simple rule: Is there an existing Jira issue named in the subject? If yes, then the body of the email is a comment on that issue. If there is not, then the config of the handler has a project to create the issue in with description = body of email. That's it. (Ok, there's some…
-
You need to think about what the customfield is returning in line 2 - whether it's nothing, null or an object that you can actually perform a "-1" operation with. As Colin says, the logs should contain a stack trace which will tell you what is going wrong - have a look at that.
-
You need to find or write a plugin that provides a workflow post-function for "copy user picker field to assignee". I think there's one in the Jira Suite utilities and/or Jira Misc Workflow Extensions