Comments
-
You have not explained what VSM is or how it applies to Confluence. And unless you're working at relativistic speeds, a minute is a minute.
-
Could you explain what this has to do with Atlassian products? (Other than you're reading something using Sourcetree to view some code for a non-Atlassian application)
-
JQL is for finding issues, it has nothing to say about what a report, gadget or process does with the list of issues it returns. Internally, it really does just return a block of issues, nothing else. So, the short answer is "no". The longer answer is "this is something that should be done by the gadget, not the filter",…
-
If you set up your defaults relatively baselined (i.e. optimised for the projects you want to create from the other system) , then you could minimise the work you need to do in any plugin/script etc. Have a quick look at the "add new project" screen to see the basics of what a project needs to be set up.
-
No, you'll need to write something. I suspect this is because it's a potential disaster, and quite complex. Creating a project requires a whole batch of configuration, and, if you did it by email, what happens if someone sends you 30 emails? You sure you want 30 projects? There's a lot of coding to be done, and I suspect…
-
I'm sorry, that doesn't make sense - you've chosen the project already when you are creating an issue.
-
Yup, that's perfectly clear, thanks.The link I gave covers it. Although there is the option it barely mentions - put the field on all screens, but give it a "context" of just that one project.
-
I'm not sure "issue template" makes a lot of sense in JIRA, but based on my guess at what you mean, try https://confluence.atlassian.com/display/JIRA/Configuring+Fields+and+Screens
-
I'm afraid you are stuck then.
-
To do that in Confluence Server, you'd need to edit the template that provides it (code change, albeit minor), or change the theme to something that does not include it. I don't think you can do either of those on Cloud.
-
Yes, that's correct - you aren't logged in, so Confluence serves up a login page (in html) to ask the process to log in. How are you doing the username:password part of the wget?
-
Ok, great, so the browser is getting the right file. So I don't know why wget doesn't. What does the file that wget actually saves say?
-
OK, you're doing something differently to me then. I get the file I ask for. Two further questions - * What do you get when you use a browser to hit the same link? * When wget fetches html, what does it actually say? Open the file in a browser?
-
You did not explain that in the original question. You only asked how you use wget and I told you. Now you've changed the question to something totally different, I can try again, although the answer is basically the same - hit the url for the file with wget and a username and password. The problem you're having is…
-
Give it the user name and password for someone who can see the page, and the url for the attachment you're trying to get. wget user:pass http://yourconfluence/pathtoattachment basically
-
What do you mean by "reduce some insight into the queue" and "see some queues to selected users"?
-
I suspect you'll find it gets closed as a duplicate of https://jira.atlassian.com/browse/JRA-10348
-
That's not true - you don't have to move issues in a "created" state and you can easily add conditions as you go through processes. And you really should check your data that's going to be hidden, or you end up with users saying "but I put in X and it's gone"
-
No, it's prompting you for information that may be needed at the time of the move. If you force it to use a specific screen, you open yourself to the possibility that you might be hiding fields that it requires you to fill in. Or missing the warnings that your existing data will go.
-
My guess is that:For a "create" screen, you are using your customised screenFor the "edit" screen, you are using a different screen, which you have not added tabs toFor a "view" screen you have fields on the tabs that have no data, AND/OR you are using a different screen, which you have not added tabs toHave a look at the…
-
;-) Not that I can find. You can still insert tabs of course, but hacking around with the core code is the only way I can find to move a custom field into the panels or get a new panel in place. I may be behind - I've not really tried it since 6.2
-
Yes, that's what Ferenc and I are saying.
-
Ferenc is correct - the issue view screen is effectively divided into two parts - one where all the "system" fields are placed and then a section devoted to custom fields. JIRA has no way of knowing where you might feel like placing completely arbitrary custom fields so it keeps them all in one section. Within that…
-
I have to say that the handful of documentation issues I've raised with support.atlassian.com have all been fixed or improved really quickly. I'd like to see a dedicated support request type for it though, if that's going to become the official way to do it.
-
Ugh, pictures instead of logs. That timeout could be any number of things, but the most likely culprit is inadequate hardware - JIRA + Plugins do require quite a lot of oomph to get going. Start with a look throuhg https://confluence.atlassian.com/display/JIRAKB/JIRA+System+Plugin+Timeout+While+Waiting+for+Plugins+to+Enable
-
You don't, natively. You'll need something like script runner or a connect add-on that can issue the multiple calls to do it for you.
-
Now that's a totally different question! But it is clear, and it is possible.Just drop the new status off the board by removing it from the columns.The downside of doing that is that it won't appear on your scrum board - you can plan the issues, drag them into the sprint, start the sprint, and then go to work mode and see…
-
You need to edit the workflow and change the first state to what you want it to be (it's the state at the end of the "create" transition). It's not a "default" really, it's what "create issue" does...
-
It's a process of getting a renewed licence for your software.
-
Yes, there's often a new one