Skip to main content

Home/ SoftwareEngineering/ Group items tagged JIra

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
kuni katsuya

[#SHIRO-160] Flex integration with Shiro - ASF JIRA - 0 views

issues.apache.org/...SHIRO-160

Shiro Flex integration security

shared by kuni katsuya on 09 Aug 12 - No Cached
kuni katsuya

[#ANN-140] Discriminator column not supported with JOINED strategy - Hibernate JIRA - 0 views

hibernate.onjira.com/...ANN-140

java JPA inheritance mapping Hibernate

shared by kuni katsuya on 20 Nov 12 - No Cached
  • Hibernate does not need a discriminator
  • because Hibernate is better than these other inferior implementations
  • It is allowed for
  • ...2 more annotations...
  • inferior implementations
  • of the JOINED mapping strategy which require a discriminator
kuni katsuya

Assigning Sprint while editing a ticket - Atlassian Answers - 1 views

answers.atlassian.com/...-sprint-while-editing-a-ticket

jira database schema

shared by kuni katsuya on 07 Jan 13 - No Cached
  • Assigning Sprint while editing a ticket
  • it is supported
  • add the "Sprint" field to the Edit issue screen
kuni katsuya

How to search issues from specific Sprint - Atlassian Answers - 0 views

answers.atlassian.com/...ch-issues-from-specific-sprint

jira sprint GreenHopper

shared by kuni katsuya on 07 Jan 13 - No Cached
  • to find issues from a specific sprint, you have to add one of the following to your JQL query: 1sprint = ID 1sprint in (1,3,4)
  • have to know the ID (not name) of your sprint.
kuni katsuya

Start multiple sprints simultaneously - Atlassian Answers - 0 views

answers.atlassian.com/...ultiple-sprints-simultaneously

shared by kuni katsuya on 07 Jan 13 - No Cached
  • one 'Planning' Rapid Board that selects all of the issues you wish to work
    • kuni katsuya
      kuni katsuya on 07 Jan 13
       
      overall product backlog
  • two other 'Work' Rapid Boards, one for each team
    • kuni katsuya
      kuni katsuya on 07 Jan 13
       
      scrum team-specific rapid boards
  • "project = x and component = TeamA"
  • ...4 more annotations...
  • "project = x and component = TeamB"
  • parallel sprints labs feature
  • Unfortunately this will make the velocity chart less usable because velocity is heavily based on the estimations of an individual team
  • scenario of having multiple JIRA projects containing work items to be picked up by / distributed to multiple scrum teams
    • kuni katsuya
      kuni katsuya on 07 Jan 13
       
      exactly our scenario!
kuni katsuya

Release Notes - GraniteDS - Version 3.0.0.M1 - HTML format - Granite Data Services - 0 views

www.graniteds.org/...ReleaseNote.jspa

java javaee javaee6 graniteds GraniteDS3 ReleaseNotes

shared by kuni katsuya on 13 Dec 12 - No Cached
  • Release Notes - GraniteDS - Version 3.0.0.M1
  • GAS3 does not handle Java generics with abstract class implementations
  • Generated as3 has compilation warnings: missing constructor
  • ...1 more annotation...
  • Rename flex-filter to server-filter and @FlexFilter to @ServerFilter
kuni katsuya

Collaboration Best Practices - 3 Reasons Interruptions are Hurting Your Team's Producti... - 0 views

blogs.atlassian.com/...nterruptions-hurt-productivity

agile productivity anti-patterns

shared by kuni katsuya on 01 Nov 12 - No Cached
  • Interruptions Hurt Your Team’s Productivity
  • Productivity is futile in the face of constant interruptions
  • work is scattered through shared network drives, hard drives, and email
    • kuni katsuya
      kuni katsuya on 01 Nov 12
       
      or sharepoint, confluence, jira, word docs, pdf docs, spreadsheets, walled post-it notes, emails... not universally or easily searchable. arghhh...
  • ...17 more annotations...
  • Charging towards a common goal is difficult when:
  • center on meetings alone.
  • When disorganization and uncertainty is the norm, clarification and re-clarification is needed to regularly keep a team focused and working together
  •  waste A LOT of your time
  • Information isn’t located in a centralized place so it isn’t easily accessible to everyone.
  • It’s just easier to ask someone else because they are a Subject Matter Expert (SME). Both.
  • 2. Interruptions encourage multi-tasking, which is bad
  • 1. Most interruptions are trivial and could be avoided
  • it takes most people 16 minutes to refocus after sending an email while doing other work
    • kuni katsuya
      kuni katsuya on 01 Nov 12
       
      it takes most software engineers *at least* 20-30 minutes to get back into 'the zone' following an unrelated distraction
  • No wonder people like to work from home!
  • To perform at your productive best, you need your best focus, something that’s unachievable when you’re constantly interrupted
  • 3. Recovering from interruptions takes longer than you think
  • Between email, meetings, and interruptions (both active and passive),
  • there’s hardly time to get any work done while you’re actually at work.
  • Pro-Tip: Only turn on email and instant message when you need to use them
    • kuni katsuya
      kuni katsuya on 01 Nov 12
       
      ie. never?  ;) though then, you end up with 5,932 unread emails in your inbox and 113 angry co-workers!
  • To combat such interruption, check these tools 3 times a day – when you first get into the office in the morning, around lunch, and before going home for the night – and turn them off otherwise.
  • reduce the rate at which interruptions occur
kuni katsuya

NetBeansUserFAQ - NetBeans Wiki - 0 views

wiki.netbeans.org/NetBeansUserFAQ

netbeans faq

shared by kuni katsuya on 15 Jun 12 - Cached
« First ‹ Previous 41 - 57 of 57
Showing 20▼ items per page