Comments
-
That depends entirely on how you are "exposing" JIRA to CQ and vice-versa. I can't tell you a lot more than that because there's no information on what you've set up to get the systems to talk to each other.
-
No, you can't do that in JIRA - the assignee list is "valid assignees", not "a list of people that varies by who the assigner is"
-
Go to the permission scheme and look at the two rules that handle this: * Assignable user: says who can be assigned to an issue * Assign issues: says who can set the assignee In your case, you want groups A and B in assignable, and just group A in assign
-
You can't change it without editing a spot of code - there's a set of standard simple queries that are built-in and reused in a few places. It can be done, but it's worth asking why you'd want to change this particular query, as it's giving useful information. (I'd be far more tempted to add new ones than change the…
-
Yes. I can understand the starting point, but I don't like the way Atlassian default the privileges to "anyone who can log in". It's fine for open access stuff, but a large amount of the users of their software do have legitimate reasons to close some of the access, and the by the time they realise they need to do it,…
-
You need to set up the space permissions to allow "someone who can log in" to see the space, but not do anything else. Then, for people who should be able to write to the space, add them separately with more rights.
-
No. It needs to know who you are to be able to send the update emails.
-
Have you tried the JIRA issues macro? https://confluence.atlassian.com/doc/jira-issues-macro-139380.html
-
It's possible, certainly, but I'm not aware of any add-ons that do things like that in the marketplace. The simple answer is to do something external - something that monitors stock prices and has rules for when you want a new issue, which then runs a simple REST call into JIRA to create the issue.
-
Excellent, that's exactly what we needed to know, you have proved that your entire email routing and delivery works fine. So, yes, there's a problem with what is being sent and when by Confluence.The next thing to look at is what you are expecting. You've said "we have set up email notification", but what is that for? What…
-
Do you get test emails that you can send from the email server setup screen? Do errors occur when you try that send?
-
I have no idea what that means, sorry.
-
You'd need to rewrite part of Service Desk.
-
Yes, it does, thanks.You are using Service Desk. That's pretty much the point of SD too - it's a *simple* flow between user and helpdesk agent. If you want the customers to give you more, you need to make them JIRA users. (Although you can, and should, customise their "create" screens so you get all the information…
-
I'm sorry, the question is unclear to me. What's a "dynamic field" - do you just mean "field"? "When customer clicks on view the full request" - I assume they've had an email notification and clicked the link to the issue? After that - "requestor action needed to ...." is nonsense, can't begin to guess what you're asking…
-
It's covered in the docs - http://confluence.atlassian.com/display/JIRA/Migrating+JIRA+to+Another+Server
-
>Once you have done this, you will be able to edit your resolution. No, you'll also need to add resolution to the edit screen. Then you'll be able to (bulk) edit it. But, if you do that, you're opening up the possibility that another user could break their issues just by editing. So if you're going to do this, you need to…
-
It sounds like your workflow did not take account of the resolution field. A workflow can be divided into two parts - not done status (usually the blue and yellow status) and done (usually the status that are green). When you move an issue from "not done" to "done", your workflow should either * Use a transition screen…
-
You need to explain what "submit date" is. Do you mean the issue created date? Or something else?
-
Ah, sorry, I don't think Dieter is right here. Unless it's changed in version 5, Summary is one of the tiny handful of absolutely mandatory fields. (The others as far as the user is concerned are project and type, and some others spring into being because of that - created and updated, the issue key and the status, for…
-
I'm not sure how the metadata stuff stores its data, or how the searcher for it works.
-
What type of field is it? Most fields will not actually take a blank string as valid content, internally, they'll go "oh, nothing, ok, I'll store it as empty"
-
Have you added "Time tracking" to the create and/or edit screens for the sub-task types?
-
Ah, ok, there should be a (rather easy to miss) link for "already got JIRA?" That should take you to a very similar looking list of downloads that actually get you .obr files instead of installations!
-
The application package just contains the application, not the JIRA framework, so it won't overwrite anything. However, the fact you've got a zip file suggests you have not downloaded the application package. It should be a .obr file.
-
No. You go to manage applications and add JIRA Software. It'll ask you for licences, or you can go into licencing via manage applications. That assumes your JIRA has access to the internet to do all the work for you. If it does not, then you will need to add the add-on by hand, which is a bit more of a fiddle - you'll need…
-
Not quite (although I think this is a matter of language rather than understanding). You don't really "buy JIRA Software". It's not paid for as a Software package, it's done by users. You can add the application to Core now, via Admin -> Manage applications, but to use it, you'll need licences for the users. Yes, your JIRA…
-
There is no "migration" to be done really, unless you're moving between servers. JIRA Software is an application that you can add to JIRA Core. (The download for "JIRA Software" is actually JIRA Core with Software pre-installed for you). If you add the application to your existing installation of Core, all the functions…
-
Yes. To create a request, you need to be a Jira user.
-
Ohh, that would be very nice. :-)