Comments
-
Mmm, useful, but it would be better to fully understand permissions first, especially as this one appears to be a missing permission rather than one that we can't work out why the person has it (which that plugin is really good at!)
-
Good, sorry it took a while to get the information straight in my head. It does sound like you've got everything set up correctly, so the next step, if possible, is to look at Bob's view and check the admin cog. Make sure Bob is looking at a project he is admin on, of course!
-
I'm sorry, I didn't explain this well enough, and I think you've not grasped what I was asking. Jira-administrators is clear, that's fine, it's "people within a specific role within a project to be able to administer elements of their projects". I am not clear whether you are asking about administration of roles, or users.…
-
Check that the people who should have admin rights definitely are in the right role in the project Check that your permission scheme is definitely associated with the right project I'm also slightly uncertain about your language - you say "only users who are in the jira-administrator group have the ability to administer…
-
Start on the network analysis to work out why you can't connect to the server.
-
Er, localhost always means "my machine that I am running the browser on". The only time localhost works is when you are on the server running Confluence. It sounds to me like you are either giving out the wrong address for your confluence, or more likely, your base-url for the server is incorrect. You'd usually access…
-
There isn't one. JIRA doesn't record "last viewed" You could think about "last updated" - if an issue hasn't had a comment, edit or transition in X months, you can consider it "old" and think about archiving it. JQL is just "updated < -365d "
-
What does "the key doesn't work" mean? I've just installed and run 3.4.3 with a newly created evaluation key and it works fine. You'll need to debug that first, then import your 3.4.3 data, then upgrade it.
-
I suspect you need an add-on for that. Worklogs don't have attributes natively in JIRA, you need something to implement that functionality (probably in a similar way to Tempo's method!)
-
All you need to do is run a query in Jira - don't bother messing with the database, a simple Jira search can do it already. Once you've done the search in Jira, look at the top of the screen for the various displays for it - if you want to get it into another application, the XML link is very useful. If you need to get a…
-
My understanding is that putting the attachments in the database was a kludge from the start, a way to try to get Confluence Clustering to work. It makes the databases far too large to be usefully backed up as soon as you get to a medium/large system and it's unweildy in terms of the things Confluence tries to do with…
-
Take the attachments out of the database and put them on local storage instead. You'll need to do that in the long run anyway - attachments in the database will not be supported soon.
-
Yes, as long as you are on JIRA 7 or above. In "manage applications" you'll find you can allocate groups to Core and Software separately. (If you're on JIRA 6, this would be a good reason to upgrade - you'd need 250 JIRA+Agile licences to achieve the same)
-
That really does depend on how you want to do it and what you want.You can try to do test cases inside Jira, or you could link it up to another test management suite. You could use Confluence to document test cases, and/or Bamboo to run them. Or do something else.So, it comes back to what you're looking for. Atlassian does…
-
Possibly. Depends on what you mean by "test management", "development package" and so-on. I'm afraid your question is a little unclear, and it would help if you gave us a little more detail on what you're trying to do.
-
Only the licence is a trial thing, the software is functionally no different to a production instance. (A trial system will simply stop working when the licence runs out) I suspect you are trying to install add-ons into Cloud though. You can't do that. Some can be added via your account, and trialled there. Connect add-ons…
-
Ah, good, that does make sense. The thing you've run into here is that Jira can't cope with a "simple" change of issue type by just changing the "field" of "issue type". It's because ALL of the configuration is hung off the issue type, so when you change issue type, it has to check the validity of absolutely everything…
-
I'm not sure I understand the question - do you really mean "move" the issue (i.e. to another project and/or issue type), or do you mean "change the issue type during edit"? (Because there's a known weakness there)
-
You can do that - try the issue navigator!
-
The sort order is set in the board's filter. So there's no way to change the sort order quickly.
-
Because a quick filter is there to hide issues from the board, not change the sort order.
-
Excellent. Thanks Jamie! 6.2 will be out very soon too :-)
-
No. It doesn't log creator unless you explicitly add a field and a post-function to log it. Yet. Atlassian have this on the to-fix list for a very long time and I remember reading it's implemented somewhere for testing and a release very soon. I think it's 6.3, but we might be lucky and get it in 6.2, I can't remember the…
-
If the workflow allows for it, then yes.
-
You can. An event is fired when something happens. The event contains all the information on what just happened. What you don't have is the ability to change the code for notifications.
-
You can't do this. The event that is going out is "issue updated", which is fired on all edits. It doesn't care what has been edited, just that the issue has changed. If you were not on Cloud, then you would have the option of delving into the core code of JIRA to try to change that, or turning off the notification for…
-
Oh, sorry, I forgot, if you do want to define your own events, do that before editing the workflow, otherwise you'll find yourself having to wander off to do it part-way through an edit. Annoyingly breaks the flow of work.
-
Change of column is, behind the scenes, a workflow transition from one status to another. If you look at the workflow, you'll find every transition has a post-function for "fire event x", and you can choose whatever event you want (you can also add your own events to use there too if you need them) Then, you can use the…
-
Joe's point about dropping the actual resolved flag until the issue is actively signed off is another approach I take quite often - it forces people to do the sign off quite neatly, although I tend use a different status than "resolved". Something like "waiting sign off" is more clear.
-
No, the point of "resolved" is that the issue is done and doesn't need more attention. The gadget is hard coded with a filter for "assigned to me and unresolved". You are right in that you can add another gadget - that's the only way you're going to do this (without code). Create a filter for just "assigned to me" and…