Comments
-
Ok, You need to create or obtain an attachmentManager object in your code, then you can use the function getAttachments(Issue) to get the list of attachments. You can then get some more information from the attachment objects - getAuthor, getFilename and so-on. There's no md5 function built-in, you'll need to code that for…
-
The field does not have a value. You need to work with a file that Jira needs to retrieve for you which is very different from a field value. Could you explain exactly what you want to do with the attachments here? For eample, do you need the information about where the user is uploading from? The content of the file? The…
-
It carries most of the config (all the bits stored in the database at least), and the licence details too, but it'll spot that it's on a different server and ignore the old licence on import. One of the things I've always liked about Atlassian is that they strongly believe your data belongs to you and they don't drop bits…
-
The good news is that you don't really have a big problem. Your data is just your data - if you import the whole lot into a new Confluence, it'll work fine with a 500 user licence as you'd expect. It'll also work fine with a 100 user licence, unless you have more than 100 *active* users. If you are over that 100 limit,…
-
See https://confluence.atlassian.com/support/atlassian-support-offerings-193299636.html
-
You can't, if you really do mean "answers", because you don't have a access to the code. If you mean one of the other atlassian systems, then it is a code change, but you will need to tell us which one for more help.
-
I'm nto a javascript expert I'm afraid. I learned very early on to avoid javascript tweaks in Atlassian products because they're an utter nightmare to get right and even worse to maintain. There's examples scattered through Answers though. I can't vouch for any of them but I'm certain they're better than anything I'd write
-
You'd need to hack the core code. You can use javascript, but you've got a bigger problem - that "people" area is not just assignee. Reporter and any other user fields you might define will end up in there. You'll also need to think about moving all the other right-hand bar stuff around if you want to get more horizontal…
-
Ah, well hunted down! (although it might be interference between that and whatever the c.a.j.plugin is) No risk in having it disabled, but you do lose the functions it provides.
-
Ok, then you need to work out what add-on c.a.j.plugin refers to. Take a look in the plugins directory in the installation and see if there's anything in there. Also, try increasing logging - add c.a.j.* as it's own line in the admin->logging and profiling section.
-
No, it's not a system addon - they all have keys starting with com.atlassian, not c.a.j. At a guess, I'd say it's the Gerrit add-on, but that's from a very quick look at google.
-
You need to upgrade the add-on to a version that works for JIRA 7.0.10. There may not be one available, in which case, it would be better to disable the add-on until there is one.
-
What is the rest of the error message?
-
Well, posting on a two year old question isn't really that useful - you're relying on the watchers to pick up, and things have changed in the last two years.Text field multi-line is the newer name for "free text field (unlimited)" and it does have wiki markup - check the field configuration for the renderer in use.
-
Use a "Free Text" field. You then need to go into the "field configuration" for the project(s) and check that the field has the "wiki markup" renderer set, rather than "text".
-
If you're willing to find/write plugins, some people set security levels in their create-issue post-functions. As you can have different workflows by issue type, you can do things like "set security to level 4 if it's a bug, and level 2 for an improvement" If you do it like this, I'd like to gently nudge you to look at how…
-
No, you're right, you can only assign issues to users, and they have to be active. Service Desk has the concept of "customers", which don't take up licences, but they're not JIRA users, they get a very limited view of the system.
-
I think the main problem is the defaults that Jira ships with make untangling the permissions and setting it up so you can do "user only sees their project(s)" quite difficult. And hard work if you've evolved lots of permission schemes. Thing is, I don't think it's that uncommon to want to do that. In an ideal world,…
-
No, the flexiblity in the scheme makes it complex to set up. You've already got a link to one attempt to set it up, but to summarise it, what you need to do is 1. Have a group that means "can log in", and does NOTHING else. (The default is to have this as "jira users", which is then used in other places) 2. If you want to…
-
For OnDemand, your only real option is the cascading select field. You can't play many of the tricks other sites use to do it (although I'd avoid it anyway, as a lot of them insert javascript in the ui, and that's always a vile thing to do with Atlassian apps)
-
No idea, you haven't explained where you're seeing this, what it is or what you've configured.
-
Then you're not a space admin in that space. Get the administrators to check who is and update it.
-
Not unless you grant them the right to do it.
-
"Due date" is one of the system fields, so it will always appear. Creating a second one as a custom field is confusing and noisy, and I suspect you've realised this. I'd delete the custom one completely if you can (or at least rename it to "deprecated due date" so people avoid it) To make the system due date appear, you…
-
You'll need to do some coding - you need a post-function that can execute the external programs and import the results. I'd look at the script runner to get started with. However, I'd also recommend a look at external build and test management tools which are far better suited to running repeated tests and reporting on…
-
What test management and/or test automation system(s) are you using to run the tests? Generally, all we can really say is "yes, it's possible", but not a lot more without knowing what you're doing.
-
All issue updates (including transitions) fire "events". You can't change what is fired for system events (edit will always fire update events, comment will fire comment events etc), but you can change the post-function on all transitions to fire whatever event you want. Then there is a second layer: The JIRA notification…
-
The error message is pretty clear that it is not set up in both directions. You'll need to show us the (working) config on both sides
-
You say you "made application link" - are you sure it is correctly set up and functioning? Did you link it in both directions - an application link to JIRA in Confluence, AND an application link to Confluence in JIRA?
-
duplicate https://answers.atlassian.com/questions/44028/jira-4-4-4-user-migration-tool-process