Comments
-
Not at that level. I assume you've already found the notification scheme - that's it really. You can amend that, but it built on "events" such as "issue changed", not "change of arbitrary part of issue" So, you can do comments, assign and updated separately, but not "title change" or any form of "minor" edit - that's just…
-
Same answer. You can't do this, Jira has Projects, and that's it. If you weren't on OnDemand, you could try the "structure plugin", which doesn't really do sub-projects as such (it's close), but does handle layers at the issue level. But it can't be used with OnDemand.
-
That doesn't really sound like sub-projects are needed. I'd move the QA out into it's own project and link the QA items to the development items in the project. Even if you had sub-projects, you'd still have to do that anyway, so there's no benefits there anyway. The other (messier IMHO) option would be to do QA within the…
-
Jira does not have sub-projects. The general answer to this question is "use components to define the parts that you would sub-project", but that only works for some cases. If you describe the structure you're aiming for here, you should find people have several suggestions for workarounds.
-
It looks like your add-ons are of the wrong version - could you check that the Tempo add-on is valid for a start?
-
Sorry, the "can use" for groups is set in "global permissions", not a space thing.
-
Yes, you can do this, but you're going to have to work through your permissions. Your user needs a simple "can use" permission, which means being a member of a group that has that global permission. The simple default case is that everyone is put into "confluence users" which has that right. But this group is often used in…
-
I'm not aware of anything that will do this - you can easily find unassigned issues, on all sorts of ways, but there's no drag and drop type screens (Even from plugins). I suspect it's because pulling issues around screens is seen as a status update rather than other data, and you've got the problem that there could be a…
-
That's another good point - you can do quite a lot of automation. Even without complex plugins, you can do things like set an assignee from other fields (If, for example, you set a "QA person" field when the issue is created, you can copy that to assignee when moving into the testing part of the workflow)
-
Who is responsible for what work is important in Jira. The core of this is the "assignee" field - Jira works on the assumption that the person named in that field is the person currently working on and owning the issue (and then workload reporting and so-on follows on from that) You can add more fields to capture more…
-
Ok, that's cleared it up. The problem is simple - "Address X_2@company.com belongs to same email group as X@company.com,". It doesn't matter about the email group, that's not of any use because it is not the cc in the email address. It's a group which JIRA has no knowledge of, and, even if it did, there's no information on…
-
It should include cc users, yes. I'm afraid I don't quite understand what you are actually doing in your question though - it sounded like you wanted the users to come from the distribution list. Could you explain exactly what the difference is between the emails that work and fail? Exactly who do you send the two emails…
-
That's correct behaviour, if I understand it correctly. JSD doesn't and can't know who else is in an email distribution list, so it can't add them.
-
The usual trick is to create a permission scheme that says "browse: well, no-one really", and use that for the project you want to hide.
-
A downgrade might not help (and may just damage your data). I'd suggest raising a support call with Riada to get their help finding your invisible data.
-
There's several options, but a lot of it depends on your process, data and how you want to do it. First thing to point out though - Jira is not a CRM system, it is an issue-tracker, it's not designed or built for handling loads of customer details, so any solution is not going to match a CRM system. Here's a few ideas: You…
-
Wrong table. You need to read customfieldvalue for the id which represents the current option. Then you use that to read customfieldoption to see what the label for the option is at the moment (the column "customvalue" holds it if memory serves)
-
No. Atlassian are looking at making project admin rights more localised and granular, but at the moment your project admins can only admin users, versions and components.
-
You can do this for issues, but you can NOT hide a project and expose the issues in it. A user MUST be able to see the project to see issues within it.
-
No, you can only edit the issue type if the configuration for the source and target types are the same. If they're not, then JIRA has to consider all of the configuration so that you don't put an issue into an invalid state during the change, and rather than re-invent the wheel, the answer was to re-use the "move"…
-
I think you should start with Atlassian support at https://support.atlassian.com (We're a community of end users, like you. We try to help, but we're not support)
-
Definitely the browser sending something odd across then!It's not my macro though. I couldn't code anything that clever, just the odd simple macro or report.
-
402 is a weird one to return. Does the map you're trying to load work in a browser?
-
Not quite how it works. Your agile licences are now Software licences which allows all those users to use Software + Core. If you want a set of Core-only users as well, then you probably want to get a set of Coe licences for them separately. Yes, you could use the "spare" licences, but they will give than software too. So,…
-
Go to the planning/backlog view in a board, click "create sprint"
-
If you read the issue history instead, you'd have access to all the changes of assignee in the same place as all the status changes. I suspect that would make it easier in general, but if you stick with os_workflow for the status information, you still need to read changeitem and changegroup for the changes of assignee.
-
Go to search issues and run something like updated > startOfWeek("-1") and updated < endOfWeek ("-1") That will get you a list of all the issues updated last week. For a more simple "updated in the last seven days", try just updated > -7d<br><br>In both cases, the issue navigator can then show you the fields you want (I'm…
-
I know quite a few sites who automate user stuff like this. The issue collector makes it easy to create the requests outside Jira, but the places I'm thinking of set up "user" projects to track users in some detail. The basic idea is that "user = issue". So you have one issue per user, and you can track them through the…
-
Remember that Jira doesn't have user fields as such, so you'll need to think about how and where you store any data captured from the user. Renjith's suggestion of an issue collector is good because you'd end up with a project full of user requests and their details, but Jira won't be aware that any of that data is really…
-
That sounds like your browser or computer has been configured in an unusual way. JIRA gadgets don't move around on dashboards unless you click them to move them first.