Comments
-
Portfolio handles resourcing and planning but not quite the money behind them. Tempo Books is probably closer to a budgetary tool, as it lets you put monetary costs on resources.
-
I'd go with Daniel and Joe as well. The problem with having Closed//deferred is that Closed really does tend to mean "dead, we're not going to do anything with this ever again". In most process flows, you probably want it separate from Closed, simply to say "we're not going to do this yet, but we will go and look at it…
-
>say someone added a condition to a workflow/transition which queries JIRA projects (all) As a JIRA admin, I'd remove it, and educate the person not to do things that break the systems. Prevent rather than plaster over a crack.
-
I did a very basic one of these a while ago - a simple script that found every document in a (doesn't)Sharepoint, ran <something> over it to convert it to moderately simple text, and then create it as a page over the SOAP interface. Confluence uses REST now, so nowadays, I'd use that.The <something> was the fiddly part -…
-
There's a bit of a jump when you move from Sharepoint to Confluence. The reason I say that is that the two systems are really aimed at two different approaches to presenting information to users. Sharepoint is very much towards doing things as a "Document management system", whereas Confluence is far closer to a "wiki"…
-
It's correct - removing the stories changed the sprint during execution, so the velocity chart is representing that.
-
I can't really tell you that, because I don't know your structures or requirements. I can only give you the general approach:1. Decide WHO really needs to see an issue update (your business rules)2. Decide HOW you identify them in JIRA generally (Reporter, assignee, member of a role in the project - those are the three…
-
I'm not quite sure that there is a question here. You've explained the scheme perfectly - on Create, it sends mail to the assignee, reporter and anyone watching the issue. I think the only thing you've missed is that you can edit the notification scheme, although I suspect you already understand it (hence why I'm not sure…
-
I'm not sure you understood what I'm getting at here (My apologies, I know my writing style is unclear a lot of the time. I find it difficult to translate the patterns I see in my mind into plain written English) You need to define somewhere to keep the file. You keep saying "upload this file", but what do you mean here?…
-
I don't understand what you are doing here. There are three possibilities I can think of: 1. The screen shot seems to show that you are using the link section. This is for linking to external urls. It does NOT add files to Jira, it really is JUST a link to a url. You'll need to be hosting the file on a server which…
-
Correct, a "release" is very clearly defined as "the current content of the 'Done' column". That's not strange at all, it's what Kanban does.
-
Ah, ok, well the short answer is "you can't". You can technically cluster your servers, but you won't be able to cluster the application. The best you can do is an active/passive failover.
-
Could you explain what version of Confluence you are using? Confluence Server Confluence Clustered Confluence Datacentre
-
Converted it to an answer because I think Sam has said exactly what it is. A brief analysis: Mary's role here is actually irrelevant, so we can ignore a lot of the question. There's two sentences that matter: * John is working for another project also which is having JIRA project name as "Jira-PA" with same view/add…
-
You need to actually have a licence before you can upgrade it to more users. The answer is still yes - you can upgrade the number of users at any time, by the method Razaq described.
-
I've worked in similar environments for years. I've always found education to be the better route than enforcement, but there are times when you just have to do it.
-
It's better to use Conditions later in the workflows - that stops people from having the option to close them, whereas a validator would let them start the close process and then give them an error message, which is not very friendly. Also, you don't need any coding for Conditions for groups or roles.
-
There's no easy way to stop users creating certain issue types (you can play tricks in the workflow like having validators or screens that fail, but that's very ugly for them) The best answer is actually to educate the users to do your process properly. On the second point, that's easier - change the workflows for the…
-
That doesn't change my answer (although, have you tried a "labels" type field?)
-
So you don't want a field that behaves like versions. You want a select list with a more whizzy renderer. I believe there's a trick somewhere - you can persuade a select list to use the Atlassian "autocomplete" renderer, but I think you have to write a custom field plugin to provide a select list that handles like that.
-
Have you tried adding a custom field of type "version"?
-
It's not finding a valid installation of 6.2 in /data/opt/atlassian/JIRA - are you sure that's where your 6.2 was installed?
-
It's pretty much what I see too, I won't repeat what Udo says.
-
No. They are web applications and dynamic, so you need to have them running to see their data. "Offline", in the way most people mean it, is useless and irrelevant. Disaster Recovery is a totally different thing. If you are running your own servers, then your Jira/Confluence licence includes provision for failing over to…
-
No, but you can export the issues it shows to CSV which Excel can read. Just go to the issue navigator and use the same filter the board uses.
-
Ah, I'm afraid you won't get it either. The built-in handlers do not have functions that allow you to set components. You'll need to write your own listener or find something to help you with it. The JEMH is always worth a look for clever handling of incoming mail, and I think you could do something with the script runner.
-
You pick one of the approaches I've discussed. The reporting does tell you when you break planning by introducing unplanned stuff. The planned guideline shouldn't change - if it did, then you wouldn't have anything to tell you what you really planned.
-
The easy answer remains 1. If somthing goes "bang", then it should be in systems you can plan for, so it's either not your problem, or you should have planned for it. A lot of places handle it with Support teams or DevOps that are separate from the development teams. Developers can then plan, and yes, even when it is…
-
The standard answers are quite short: * Don't. If new work arrives, do it in the next sprint. You've planned against a set of tasks, do them, and ignore new stuff. * Accept that it is mis-estimated and keep announcing that the work is breaking your plans * Plan for it. Have a look over the last few sprints and how much…
-
Oops, yes, I missed that one, sorry!