Comments
-
Oops. Chander beat me to it! Sorry!
-
I think you're confusing a script with a behaviour. Formfield is not a script object, you'd actually want to use custom field objects. Or, as it's groovy, the easier option of just "def something = x". In fact, you should just enter return getCustomFieldValue("A") + getCustomFieldValue("B") in the scripted field and set…
-
Well, the actual path is up to you.I find it a lot safer and easier to copy and upgrade, when you have the hardware to do it. A good, safe path is:- Setup Jira on the new server, check it all runs, and do all the upgrade testing you can- Delete all your test data on the new server- Stop Jira on the old server- Copy the…
-
Yes, you can upgrade to any version released before the end of your licence. 4.4.3 to 5.2.2 can be done in one step - see https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA for the details.
-
Two OnDemand instances are separate systems. You'll need to manually duplicate the users from one system into the other.
-
Remember that this can give you many projects and sprints - sprints do not belong to projects, or vice-versa, it's a many:many relationship.
-
Ah, ok, I'm not familiar enough with it to be able to tell you what reporting it might be able to do, or how it affects JIRA issues in ways that you could use for reporting.
-
How are you implementing these "test cases"?
-
You can't. Jira natively doesn't log this activity in 6.1 or below. Some tracking is implemented in 6.2 (I've only glanced at it so far, so I can't tell you how comprehensive it is. Looks like it covers a lot though). So, if you're not on 6.2 (i.e. OnDemand), you're probably stuck. You can do things like ploughing through…
-
Start by raising a support request with Atlassian at https://support.atlassian.com- they'll talk you through what you need to do. (We're not atlassian, we're end users like you. Atlassian are here, but you need a formal contact for this, via their support desk)
-
Macros are part of pages, not logins. The only way I think this is going to work without changing the core code is to change the Confluence dashboard setting from "dashboard" to "specific home page" and make it land on a page that includes your macro.
-
I'm not sure. You'd need something to parse their user details to work out their company from something in <span class="com">$action.remoteUser </span> (I assume it's part of the email address for the user?). Then it'll need to embed a redirect, which is out of my skill range (I don't do javascript beyond reading it and…
-
There's no function for that in Confluence, but I suspect you might be able to write a "user macro" that will look at who the user is and issue a "redirect" to the correct page
-
That looks like a Portfolio view - have you tried adding the Portfolio add-on?
-
Yes, sort of. Your users will need to be JIRA users (not agents) and then flagged as "collaborators". Have a look at https://confluence.atlassian.com/servicedesk/collaborator-660967501.html
-
It's correct for connecting to older versions of JIRA, I'm sure it will catch up when the last version of JIRA 6.4 goes out of support (spring 2017) and only 7 onwards is supported.
-
Ah, I see. No. The Edit function does not have post-functions. Your options are to move Edit into the workflow (so don't allow your users to edit directly, just move through the flow) or do your link additions as a listener instead of a post-function. A listener can pick up "issue updated" events thrown by the edit…
-
Ok, so what's the post-function relevance, and what are you actually trying to do?
-
I'm not sure what the question is here - you've talked about a post-function to add links but I don't know what that has to do with the edit in the workflow (or even what "edit in the workflow" means - do you mean the transition screen where you can update fields during a transition?)
-
You can't - there are (potentially) many worklogs for each issue, so you'd get many worklog dates and creators out if you could export it like that. But you can't get it - the excel export is for issues, not worklogs. It can give you summaries, but because it's for issues, it can't go down to worklog levels. For worklog…
-
No, the backup facility really isn't designed for backups in that sense (Atlassian do backups internally so they can continue to host OnDemand if something goes wrong). It's designed to allow you to take a simple full backup of everything when you think you need one.
-
No, there's no structure in JIRA for what you've vaguely defined as "sub sites". A standard answer here might be to look at the use of components in projects, but I'd also suggest you have a look at project categories. You could have a set of project categories, one per "department", and then have schemes that separate out…
-
No, you can't limit the group visibility to "same as me" Atlassian have not even tried to implement it. It is a bit of a pain for certain cases, but there's massive logical problems with implementing it. Off the top of my head: * The default in JIRA is to have a group for "user can log in". All (active) users are in it. So…
-
Yes, I think it's possible, but I can't see an API method to do it - you'll have to loop through all the transitions in the workflow until you find one with a matching name. (And deal with "no transition found because the name has changed" - I'd just fail gracefully and silently, but it does mean you'll need to explain…
-
The name of a transition is even more likely to change than the ID. I'm not sure there's any mileage in using the name over the ID. Also, Atlassian have issues logged to enable translations of names, so a single transition, with one ID could end up with several different names. I know the API lets you get a name for an ID,…
-
Ok, you're using a connector that is written by Mulesoft. I'm not familar with the connector, but google implies there are some issues with it, and you probably need to talk to Mulesoft as this looks like a bug in their connector. Or, it might be a simple "not able to connect" and an unhelpful error message. Can you test…
-
I'm afraid whatever "connector" you are using has a bug then. Jira's SOAP interface has been tested extensively and all the bigger bugs found and eliminated, it certainly isn't exposing any broken data. So the error must be on the connector side. Which connector is it? Where are the docs for it?
-
It depends. What is Mulesoft expecting Jira to do? The string you've given for the SOAP interface looks correct to me, so you've kind of answered your own question - you just need to change it to use your Jira server. Also check that rpc remote calls are enabled in Jira's Admin -> general setting screen. The error you're…
-
Right. There's something *very* wrong here, and it's not something you are doing, it actually feels like something has hacked the create process.Could you check PR-17 again (I am assuming that PR-17 is supposed to be a sub-task?). What is its issue type? Also, as an admin, could you go to to Admin -> Issues -> Issue types…
-
Ok, and when you do that, does it offer you a list of issue types to choose from? What is on that list? I'm just checking that you are definitely landing on the sub-task create, because it sounds like you're somehow not creating subtasks at all.