Comments
-
What does the board filter say, and does an issue "done" this way still match it?
-
That would need a lot of fiddling to bind the services to different IP addresses, and I'm not even sure they'd be able to all run on the same port. A better approach would be a proxy with different domains. https://myserver.org/jira https://myserver.org/conf https://myserver.org/fisheye etc. Or jira.myserver.org,…
-
No. A board is there to represent information to a team in the same way, so everyone is working from the same thing.
-
I think the only add-on that supports theming by user group is Adaptavist's Themebuilder, and even that is just about hiding or showing elements of the theme by group (i.e. it's the same theme, but parts of it behave differently for different groups of users) I would definitely look again at Brikit and RefinedWiki to see…
-
You have a development licence attached to your account if you go to my.atlassian and look at your list of licences. There's a link to generate one beneath the full licence details on the right.
-
If I have read this correctly, you seem to be pasting a block of velocity into a field in Jira. That's not what the documentation says - it says to create .vm templates, including references to the new fields you want to add, modify a properties file to tell Jira that your new files are to be used and restart it. Could you…
-
It's still unclear what you are asking. Jira clearly does "support velocity template" because most of the system uses velocity to render pages. It helps that you've actually started to tell us what you mean, but I can't see where you are getting stuck. The instructions on that page work fine in the test system I'm…
-
Sorry, I don't understand the question. Jira uses velocity templates internally, in all versions, but I don't know what you're actually asking beyond that?
-
Rather an old question to add a comment on, things have changed.The auditor plugin I mentioned is effectively built in to Jira 6.3 and above. If you enable it, it will track deletes. I don't know if it is enabled by default in OnDemand.If it is not active, then you have no way of knowing who deleted an issue.
-
If you're not using OnDemand, then there's a plugin that will audit events including deletes - https://marketplace.atlassian.com/plugins/com.plugenta.jiraauditor
-
As Penny suggests, start with a filter and a 2d filter. I went one further and scribbled a report ages ago - list of projects, with the number of issues in them and the highest number used (note that those can be different!). I'd like to add "last time issue was updated" and "when earliest issue was created" to give a bit…
-
Technically, there's a far more simple solution - use the advanced "reporter browse" permission. However, I do not think this is enabled on OnDemand...
-
You'll need to find or write code to create a condition that can check for sub-tasks and read their fields for the data to base the decision on.
-
JQL is for finding issues, not fields, so that's not really going to work. (You can't say "show me something on an issue" with JQL, the question is always "Show me the issues that match this data)For SQL, read changeitem for the <fieldname><from><to> I mentioned already, and join it to changegroup to link in with the…
-
It is in the history - every time you update a field on an issue, JIRA writes "<fieldname> <from> <to>" into the history. So if you look for the first instance of "Assignee", then the <from> will contain the original assignee. I suspect there is more to the question than "just look at the history" - could you expand and…
-
I'd raise this as a new feature request for Tempo
-
Because the body of your question differed from that, your comments talked about a different thing, and the use of the word "assign" is unclear. Which is it? * You cannot add a group to a project role * You are not seeing the members of a group you added to the role in the list of possible assignees
-
No, I'm right and your own next sentence proves it - you say it does not assign to group, but assigns to the default or last assigned user. I'd argue that the name of the function is misleading, because it still assigns to a user. However, your new version of the question is no longer about assigning to a group. It is now…
-
I'm not sure I understand the question. >I edited the permission scheme so that Browse Projects does contain the new group, show where? > the group doesn't show up as an assignable item That's correct, assignee is for users, not groups (Assign to group does not work in real life, so JIRA does not implement it)
-
But where do you want the field to appear in Jira?
-
The question was about JQL, and different issues. The code you've given adds up fields on the same issue.
-
It's important to think of where you expect this field to occur for the user - gadget? Report? On an issue?
-
I completely understandable why you ask, but this question is the wrong way around. A more useful question is "will plugins that work for 3.5 work on version 5?". This is because there is no way Confluence developers can be expected to know what plugin developers may have done and code to support them, it's a bottomless…
-
I think you need to flesh out this question somewhat.
-
What urls are you feeding into the systems? The unique IDs the systems use should be totally different, the only way I can think of getting the same one is to clone a service from one place to another, but you'd have to be trying to link JIRA to a clone of itself, not a Confluence.
-
You might mean two things by "eliminate". You can hide a page from a user by using "restrictions" to limit access to groups they are not in (or named users) You can allow them to delete pages by granting them delete permission in the space permissions.
-
I don't think the "lazy" comment is valid - you need to compare what they have delivered against what they've not got on to yet. They're very active and have dealt with many higher-voted issues than the ones still outstanding. If they delivered what you thought was critical, they would not have had the resource to deliver…
-
Right, so that simple filter works. This confirms that the problem is (almost certainly) the search that you are running. You need to change your search so that it only searches for issues that the field is valid for. It does not matter if there is any data in the field, it matters if the field exists. You need to include…
-
I'm trying to confirm whether you have hit a long-standing design flaw in Jira. I'm not sure how else I can explain it though. Please, run a simple filter. Pick an issue that has some data in the field you are struggling with. Run a filter for "Key = <issue you have data for>". Please do not try anything else with this, or…