Christian Czaia [Decadis AG] Expert

A server restart does the trick...

After I restarted my server (I also re-indexed the fiels after reboot) the fields did show in the correct order. Cheers Christian

I mean in general. Those fields I've created. As soon as I update the description or anything regarding a particular field the alphabetical order is ignored an the field is placed at the bottom of the screen.

Nothing really as far as I know. Stays has just been rebranded to Bitbucket server

Sorry for any confusion. Please see Darline's response. How JIRA Software licenses work The new JIRA Software application includes heaps of features like boards, sprints, and reports that are included for free with your existing JIRA license. If it's possible for your organization, we recommend upgrading to JIRA Software…

Have you tried sth. like firebug. Maybe you're getting some error info there...

Do you have a pop-up blocker that might be causing that?

Since Greenhopper 5.8 you can create (rapid) boards across multiple projects: https://confluence.atlassian.com/display/GH/GreenHopper+5.8+Release+Notes

Why don't you use the system version fields? There you have the desired behaviour...

I hope I don't get you wrong but as far as I know the WebDAV plugin just handles the files, as you said, which are phisically bound to a page without having to manage the files from within Confluence. Inserting them into a page (via macro I guess) is a different thing...

What do you mean by "no longer displayed"? Have you changed the default priorities, changed the card configuration... Do those issues have the priority on the view issue screen in JIRA? It's pretty hard to tell whats going wrong... Do you have a screenshot of your planning board?

Use the estimate fileds (or the story point field, depending on how you estimate stories) in your issue "edit screen" in JIRA

Don't you get the "Confluence gadgets" option in the menu dropdown? If i click on Browse a menu just like the one in my screenshot appears. I don't have to type in anything...By the way, you have to be on the dashboard to get the right context menu! Cheers Christian

You could look at the DB to identify the sprint: select * from AO_60DB71_SPRINT WHERE ID = 1281 After that you should find out which project / board is using that sprint. Probably a project where you don't have any viewing permission.

So what's the question?

Another workaround could be to delete those field from the edit issue screen and put them on a "global transition" that only certain groups can see. The transition wouldn't change the status but you can limit who can see it via "conditions"... Another way could be to use the behaviours plugin:…

Isn't that the designed behaviour? You link to an attachment and the links always points at the most recent doc... https://confluence.atlassian.com/display/DOC/Linking+to+Attachments

Well, if it's not on the board, you won't see it in the reports... If that's not important you could add this to the board (sub) filter: ... AND status changed TO "<Whatever is mapped to your Done column>" AFTER startOfDay(-72h) Cheers

I would recommend you read the following doc: https://confluence.atlassian.com/display/APPLINKS/Configuring+Authentication+for+an+Application+Link#ConfiguringAuthenticationforanApplicationLink-Securityimplicationsforeachauthenticationtype It's about security... Cheers Christian

Yes, just make sure that the user doesn`t have the "JIRA users" global permission. Only users that have this global permission count towards your license#.##Check the documentation: https://confluence.atlassian.com/display/JIRA/Managing+Global+Permissions

You should see the issue key of your epic issues...

Hi, there has been a similar question... https://answers.atlassian.com/questions/40782/epics-labels-and-linking AS far as I know epics are like labels. They can't be restricted to a single project. They will show up in your project summary page (labels tab) only if you use them in your project though... Cheers Christian

Cool, especially since you still have the "favourite" badge ;-)

I'm afraid you can't achieve what you want. There is no default sorting order (other than issue key). Sorting is done or can be persisted with every filter you create and save via JQL (ORDER BY). In my opinion this makes sense because what you want to be the default order doesn't neccesarily have to be the opinion of other…

You may have run into that problem: https://answers.atlassian.com/questions/152787/confluence-edit-page-in-chrome-27-look-bad Cheers

Shouldn't the closing</tr> tag be positioned before the #end Cheers Christian

What kind of custom field are you talking about? Can you post a screenshot from the configuration page?

Go to your field configuration and delete the default value / change it back to none... https://confluence.atlassian.com/display/JIRA/Configuring+a+Custom+Field#ConfiguringaCustomField-default_valueDefaultvalue Cheers Christian

http://confluence.atlassian.com/display/JIRA/Managing+Project+Role+Membership

Create a very simple workflow with just one status: Closed After creation the issue will automatically be closed. I would also set a resolution in a post-fucntion if I were you. I don't really know why you would want to do that but that would be an easy fix. Cheers