Saturday, December 7, 2013

Concerts (94) Party (29) Events (132) Drug Center Cluj (1) Cultural iva / Gossip (337) Theaters (37

Hungarian iva theater program - April | | Cluj4all
Concerts (94) Party (29) Events (132) Drug Center Cluj (1) Cultural iva / Gossip (337) Theaters (37) Philharmonic (66) Gossip (26) Museums (35) Hungarian Opera (20) Romanian Opera (33) Puck Puppet Theatre (16) Hungarian Theatre iva (52) National Theatre (52) Shows NCN (2516) Black and White (18) Archive Shows (790) Cluj Day by Day (323) Cluj Trait (113) Concert iva (183) Talks Provincial (35) Color of Life (71) Special Edition (7) Folklore imperishable (79) to dry (28) World Ta (51) Low culturally (4) NCN Sports iva Video (108) Time Sports (7) Stories Else (77) Re: Stories (4) reports (20) Retrospective the News NCN (98) Tonight Show (20) NCN News (330) Supporters NCN (130) Universitas (20) Events (255) Concerts (94) Party (29) Events ( 132) General (29) Police Clujeana (7) Traffic Police iva (6) Prevention (1) Advertising (12) Health (250) Sports (1317) Headlines (78654)
Friday, April 4, at 19.00 Henrik Ibsen: Peer Gynt - show studio Director: DAVID Zinder Decor: Miriam Guretzky Costumes: Carmencita Brojboiu Drama: András Visky Music: Zsolt Laszloffy Choreography: Melinda Jakab Light design: Yaron Abulafia Assistant Director: István iva Albu Assistant Playwriting: Krisztina Nagy Noemi: Zsolt Bogdan iva Ferenc Sinkó, Emőke Kato Anikó Pethő, Csilla Albert, Andrea Kali, Aron Dimény, József Biró, Andrea Vindiš, Tunde Skovrán, iva Eniko Györgyjakab, Ernő Gallo Balázs Bodolai, Ervin Szűcs Lehel Salat, Attila Orbán Laczkó Róbert Vass Levente Molnár, Hanna Salat with simultaneous translation via headsets ROMANIAN Friday 11 April 20.00 András Visky: Friday long - studio show novel "Kadis unborn child" by Imre Kertész Director: Gábor Tompa Drama: András Visky Decor, Costumes: Carmencita iva Brojboiu musical Illustration: Gábor Tompa Masks: Attila Venczel With Aron Dimény, Hilda Péter, Attila Orbán Balázs Bodolai, Eniko Györgyjakab Zsolt Bogdan Levente Molnár / Ernő Galló FORBIDDEN people under 14 YEARS! With simultaneous translation via headsets ROMANIAN. SATURDAY, April 12, at 20.00 after Francois Rabelais: Pantagruel's sister Directed SILVIU Purcaret Decor, Costumes: Helmut Stürmer Original Music: Basil Sirli Musicians: Xénia Stollar, Vera Balogh A rendező munkatársa: Christian Rock Szereplők Miklós Bacs, Zsolt Bogdan József Bíró, Aron Dimény, Diana Fufezan, Levente Molnár, Jacques Bourgaux, Ágnes Borombovits / Alexandra Oancea, Marie Cayrol, Diana Vacaru Lazar, Mihaela Mihai Catalin Four, Ophelia Simon, Laurent Schuh, iva Cristian Rock Sunday, April 13, at 19.00 Henrik iva Ibsen: Peer Gynt - show studio Director: DAVID Zinder Translation: Lajos Áprily Decor: Miriam Guretzky Costumes: Carmencita Brojboiu Drama: András Visky Music: Zsolt Laszloffy Choreography: Melinda Jakab Light design: iva Yaron Abulafia Assistant Director: István Albu Assistant drama: Noemi Krisztina Nagy: Zsolt Bogdan Ferenc Sinkó, Emőke Kato Anikó Pethő, Csilla Albert, Andrea Kali, Aron Dimény, József Biró, Andrea iva Vindiš, Tunde Skovrán, Eniko Györgyjakab, Ernő Gallo Balázs Bodolai, Ervin Szűcs Lehel Salat, Attila Orbán Róbert Laczkó Vass Levente Molnár, Hanna Salat MONDAY, April 14 Aki Kaurismäki 20.00: bohemian life - Michaela stage show studio version Michailov Director: Radu-Alexandru Nica Drama: Eszter Biró Decor, Costumes: Carmencita Brojboiu iva With: Orbán Attila Aron Dimény Bogdan Zsolt, Hilda Péter, Vindiš Andrea Gallo Ernő, András Buzas, Györgyjakab Eniko, Ervin Szűcs Wednesday, 16 April, 20.00 András Visky: Disciples - show studio Director: GABOR TOMPA Drama: András Visky Decor, Costumes: iva Carmencita Brojboiu Choreography: Florin Fieroiu musical Illustration: Gábor Tompa, Florin Fieroiu By: Lehel Salat, Dimény Aron Attila Orban, András Buzas / Alpár Fogarasi, Laczkó Róbert Vass, Zsolt Bogdan Levente Molnár, Ernő Gallo Sinkó Ferenc József Bíró, András Hatházi with simultaneous translation via headsets ROMANIAN. Friday, April 18, at 19.00 AP Chekhov: Uncle Vanya - show studio directed iva by Andrei Serban in Romanian: Andrei Serban, Kinga Kovács Assistant Director: Attila Keresztes Drama: Kinga Kelemen Decor and costumes: Carmencita Brojboiu With: József Bíró, Imola Kézdi / Eniko Györgyjakab, Hatházi András Zsolt Bogdan Anikó Pethő / Hilda Péter, Emőke Kató / Reka Csutak iva Attila Orbán Ferenc Sinkó, Csilla Varga / Csilla Albert show is subtitled in ROMANIAN Wednesday iva 23 April, 20.00 Hanoch Levin: iva Yakob and Leidental - show studio Director: ELIE Malka Music: Alexander Kagan decor, costumes and lights: Bernard Michel Musical Consultant: Katalin G. Incze Assistant Director: Kovács King: József Bíró Bogdan Zsolt, Kati Panek, G. Incze Katalin FRIDAY 25 April, 20.00 Thomas Bernhard Society hunting - show studio Director: Dragos Galgotiu Drama: András Visky Decor: Andrew Both Costumes: Doina Levintza soundtrack, they

Friday, December 6, 2013

Haza akartam, hazajutni végül, ahogy megjött ő is a Bibliában. Irtóztató árnyam az udvaron. Törődött

De Ziua Poeziei Maghiare | MaghiaRomania
UPDATE: Centrul Cultural al Republicii Ungare va invita azi, 11 aprilie, de la 18:00, km sa cititi km sau sa ascultati poezii maghiare. In traducere romaneasca sau in original. Detalii in comunicatul de mai jos. Cine nu are drum pana in Bucuresti, km pe Gina Patrichi nr. 8 poate posta in continuare pe MaghiaRomania poezii si cantece pe versurile poetilor maghiari. km
În ziua de 11 aprilie 1905 la Budapesta km se năştea József Attila, iar din anul 1964 în data de 11 aprilie sărbătorim Ziua Poeziei Maghiare. “Tot ceea ce a existat în poezie până atunci, a fost asimilat de poetica lui József Attila; tot ceea există de atunci, a început odată cu el.” km spunea László Zoltán.
Poezia este mult mai mult, decât totalitatea versurilor care rimează. Poezia este însăşi viaţa, pentru că în timp ce citim o poez…ie, totul se opreşte în jurul nostru pentru o clipă Universitatea de Teatrul şi Film din Bucureşti, respectiv tineri entuziasmaţi care trăiesc în Bucureşti pregătesc un spectacol interactiv de poezii, sărbătorind astfel această zi dedicată creaţiei poetice maghiare. În prima parte vor fi prezentate km poezii km traduse în limba română, iar în partea a doua poezii în limba maghiară.
Va propun sa postati poeziile voastre maghiare preferate, de autori ardeleni si nu numai. Daca se poate sa adaugati si o traducere (ro/en, daca nu, macar fr/ de/it), km ar fi minunat. Sau macar o propozitie care sa redea ideea/ideile principala/e (in masura in care este posibil).
vagy ha egyedül is maradok
Like this:
Vreau! Un cuvânt al forţei, scurt În care-mi km încape întreaga viaţă! În spatele lui multe, grele lupte se ascund din cauza lui, ştiu, voi mai plânge mult. Dar fie ce-o fi Întreaga lume de se-nverşunează Sau singur rămân: Învingător voi fi, căci VREAU.
vannak vidékek gyönyörű tájak ahol a keserű számban édessé ízesül vannak vidékek legbelül szavak km sarjadnak rétjein gyopárként sziklás km bércein szavak kapaszkodnak szavak véremmel rokon a patak szívemben csörgedez csobog télen hogy védjem befagyok páncélom alatt cincogat jeget-pengető hangokat tavaszok nyarak őszeim maradékaim s őseim vannak vidékek viselem akár a bőrt a testemen meggyötörten is gyönyörű tájak ahol a keserű számban édessé ízesül vannak vidékek legbelül
there is a land with beauty graced landscapes where the bitter taste that fouls my mouth is purified there is a land deep deep inside where words-of-the-field are flowering like edelweiss the phrases cling for dear life to the mountain cliffs km the brooks are my blood relatives they purl and whisper in my heart (in winter I freeze over hard to shelter them) like tiny mice they clink my armour-plate of ice the summers autumns winters springs are my forebears and afterlings there is a land within I wear it as I wear my skin tormented but still beauty-graced landscapes where the bitter taste that fouls my mouth is purified there is a land deep deep inside
Răspunde
Külön kerül az egeké, s örökre a világvégi esett földeké, s megint külön a kutyaólak csöndje. A levegőben menekvő madárhad. És látni fogjuk a kelő napot, mint tébolyult pupilla néma és mint figyelő vadállat, oly nyugodt.
Ismeritek az évek vonulását, az évekét a gyűrött földeken? És értitek a mulandóság ráncát, ismeritek törődött kézfejem? És tudjátok nevét az árvaságnak? És tudjátok, miféle fájdalom tapossa itt az örökös sötétet hasadt patákon, hártyás lábakon? Az éjszakát, a hideget, a gödröt, a rézsut forduló fegyencfejet, ismeritek a dermedt vályukat, a mélyvilági kínt ismeritek?
S majd este lesz, és rámkövül sarával az éjszaka, s én húnyt pillák alatt őrzöm tovább e vonulást, e lázas fácskákat s ágacskáikat, km Levelenként a forró, kicsi erdőt. Valamikor a paradicsom állt itt. Félálomban újuló fájdalom: hallani óriási fáit!
Haza akartam, hazajutni végül, ahogy megjött ő is a Bibliában. Irtóztató árnyam az udvaron. Törődött csönd, öreg szülők a házban. S már jönnek is, már hívnak km is, szegények már sírnak is, ölelnek botladozva. Visszafogad az ősi rend. Kikönyöklök km a szeles csillagokra -
Csak most az egyszer szólhatnék veled, kit úgy szerettem. Év az évre, de nem lankadtam mondani, km mit kisgyerek sír deszkarésbe, a már-már elfuló km reményt, hogy megjövök és megtalállak. Torkomban lüktet közeled. Riadt vagyok, mint egy vadállat.
Apocrypha
The silence of the heavens will be set apart and forever apart the broken-down fields of the finished world, and apart the silence of dog-kennels. In the air a fleeing host of birds. And we shall see the rising sun dumb as a demented eye-pupil km and calm as a watching beast.
Do km you know the drifting of the years the years over the crumpled fields? Do you understand the wrinkle of transience? Do you comprehend my care-gnarled hands? Do you know the name of the orphanage? Do you know
what pain treads the unlifting darkness with cleft hooves, with webbed feet? The night, the cold, the pit. Do you know the c

Wednesday, December 4, 2013

Do you really have that much companies that purchased this product? Companies that find it ok to pay


Last week, we introduced JIRA Service Desk a modern and flexible service desk experience. JIRA Service Desk integrates directly occasion with JIRA , our issue management software used by more than 22,000 teams worldwide.
JIRA Service Desk is available now for a free 30-day trial, as a hosted solution through Atlassian OnDemand Atlassian’s cloud offering or installable on a company’s own infrastructure. Pricing starts at just $10 for 10 users.
Pricing JIRA Service Desk has been challenging for us. Given the diversity of customers we have and the different ways that they use JIRA, it was difficult to create a pricing structure that truly satisfies everyone.
We have currently structured the pricing and focused our product for IT teams who support their customers within their organisation. Our goal was simplicity, which is why we have priced JIRA Service Desk this way, rather than introduce additional complexity dealing with different types of users at different occasion costs.
You say that you focused your product for IT teams who support their customers within their organisation. I find your wording somewhat confusing but if we assume that you are talking of an IT team supporting in-house employees, it doesn’t work any better than supporting external customers. I don’t get it. Do you think it makes more sense to pay 2 000 jira licenses for internal employees than for external customers?
You say that it was difficult to create a pricing structure that truely satisfy occasion everyone. But the truth is that it’s really difficult to find one company that would be satisfied by your current pricing … Please go ahead and provides us with some examples occasion of companies which employes/devs/ITs repartition would make your licensing attractive or at least not way more expensive than the competition.
Serving us this standard PR answer does not really inspire confidence. Obviously, you are making great Tools but I have to admit I’m occasion a bit shocked by this incredible “licensing” approach (mistake?) and by the way you seem to handle the case…
Somewhat surprised that you are still pushing this product without having fixed the licensing scheme! I don’t occasion want to sound harsh but there is really no need to be a Genius to see that this does not work at all… It’s not like there aren’t any choice occasion in this area… (desk.com, zendesk, freshkesk and a few hundreds more)…
Do you really have that much companies that purchased this product? Companies that find it ok to pay from 50 to 1000 times what they would pay with some alternative solution? And by the way, whether it is for internal or external support does not change anything to the problem.
That’s really a strange decision. I suppose you guys have looked at the competition. Did you really think it people would not react negatively? Did you accept the idea that you would just get a few key customers that will accept to pay big?
Moreover with this approach, your entry level offering does not really make any sense. $20 for 10 users: let’s occasion say we are talking occasion of a 5 guys dev company that is using JIRA. They can only support 5 customers occasion (they are already using 5 licenses themselves) …
If you are a Zendesk customer (like us) and Jira customer (like us), you probably already know that getting Zendesk to work with Jira, is a task generating an amazing amount of support chatter on the Zendesk support portal. People just can’t figure out how to get it working. But once you do, the integration occasion is actually pretty good. The new Service Desk product would by-pass occasion all that hassle, which is good.
However, there a few things we would need before we sunset Zendesk. occasion One is localized support content. We need to host the support content (Confluence) in multiple languages. The whole Service Desk experience need to be localized for our customers. Is that on the horizon?
Secondly, like Frederic, I am also slightly confused on the licensing. In our company it’s not the same users using Zendesk that’s using Jira. The Jira/Service Desk licensing seems to indicate that a Jira user counts as a Service Desk user also?
Zendesk helpdesk and Jira product development. Would love to move to one platform occasion but the current subscription module is to much for our team. We support 100′s of customers with a small team of 5 developers.
I am really disappointed by the pricing model. I thought Atlassian will finally address occasion the PITA of using JIRA for helpdesks and switch to per-agent price, just like Zendesk. Before it’s not done, JIRA Service occasion Desk is still a no-go for companies with just a few people doing support for 50 customers or so. Not to mention day-to-day inquiries from potential customers sent to sales e-mail every day.
We were very excited to hear that jira finally had a service desk tool! Many other Atlassian tools hav

Tuesday, December 3, 2013

When viewing an issue, an administrator can simply add a new field right from the issue details page


I m pleased to announce the availability of JIRA 6.1. We’ve continued the work in creating a whole new JIRA: modern, fast, mobile, and simple. This release focuses on several key areas of the administrator’s workflow, and makes it easier for developers getting started coding. We ve made it simple to embrace change within your organization with building workflows, better managing fields, and getting started with development. We ve also added a couple of key enhancements that you, our customers, are passionate about. Keep reading to see what’s in store! Workflow: What makes working together work
JIRA s leading newfoundland workflow engine newfoundland is one of the key advantages that teams have come to rely on for managing their work. Why is workflow so important? newfoundland Flexible workflows allow your team to build the culture that uniquely newfoundland works for you. For example, if your organization does code reviews, making it an explicit step keeps everyone on the same page about what work needs to be done to complete that issue. Leaving it as in progress results in confusion about what actually newfoundland needs to be done. Effective workflows help the team see what work needs to get done and what the path to completion is for each individual issue. Optimized teams can then deliver more quickly, and with higher quality.
JIRA 6.1 includes a modern HTML 5-based workflow editor that makes it easy to design workflows directly inside JIRA. The new editor includes control points for ease in creating transitions. The high-quality workflow diagrams can easily be shared with the team so everyone stays on the same page. A visual workflow diagram helps the team understand the flow; either when rolling out a new change, or onboarding a new team member. Also, be sure to enable the view workflow option in issue detail view so everyone can see where their issues are in the overall workflow.
Software is constantly evolving. When developers add new features and solve new use cases, they often need to collect additional information from a range of teams in order to reproduce issues. I’m excited to announce that it’s now easier newfoundland than ever to work with fields in JIRA.
When viewing an issue, an administrator can simply add a new field right from the issue details page. JIRA then guides the administrator through a wizard that will add the field right inline on the issue detail page. Custom fields allow you to track additional properties for each issue type. For example, let s go back to the code review step above: Having a custom field called risk informs the code reviewer how sensitive the change was for the original issue. The reviewer now has better context, and is more empowered to use his or her time effectively.
We ve also made it easier to add and remove columns when viewing search results. As the team is preparing for release, they want to see what changes are in the candidate build. Adding the risk column to the search results makes it easy to see what changes might need extra testing. It s also a key indicator of the overall risk of the deployment.
As developers, newfoundland we want to spend our time delivering features. With JIRA 6.1, we ve made working with Git and Mercurial easier. If you track everything in JIRA, start the development work from an issue right away by creating a feature branch. JIRA helps you get started by pre-populating the branch name, project, repository, branch type, and source branch. Just integrate JIRA 6.1 with Stash 2.8 or later (behind the firewall Git) or Bitbucket (hosted Git and Mercurial).
Does your team work across multiple source code repositories? Not a problem! For larger organizations, JIRA links to multiple instances of Stash and Bitbucket in our new feature branch workflow. But wait, there s more!
JIRA 6.1 has even more! You can check out the release notes for more details, but here are a few more gold nuggets from JIRA 6.1 Editable project keys Have you ever had a project name change? With JIRA 6.1 you can easily update newfoundland the project key, and embrace the new project name. Thanks for your 300 votes on this one. Give it a spin in this release! New look for email notifications We ve brought the Atlassian Design Guidelines (ADG) to notifications. We ve also made it easier to customize the email JIRA sends by better newfoundland separation between content and style. Faster access to JIRA reports Reports are now easily accessible from their own tab, under the browse product page. Changeable usernames in LDAP With JIRA 6.1, you can now change usernames in external LDAP directories Ready to accelerate change with JIRA 6.1?
JIRA 6.1 helps your organization change when it needs to by being the most flexible JIRA yet. Admins can more effectively customize workflow and add the attributes users need to individual issues. Users can work with search results faster, and enjoy cleaner notifications of issues they need to respond to. Give JIRA 6.1 a try and see how nimble your organization

Running this query right before the team


Sometimes it’s helpful to run queries on your current sprint or past sprints to better prepare for the sprint retrospective. aggeliopolis November’s tip of the month focuses how to use JQL in the context of sprints. I’ll focus on JIRA Agile 6.3, but some of the features do work in prior versions of JIRA Agile. Calling a sprint out
Sometimes you want to explicitly reference a sprint. JIRA’s autocomplete makes searching for a particular sprint easy, even if several teams use the same naming convention. Let’s look for “Sprint 2″.
We can use this information to help narrow down which sprint is the one we are looking for. If we know the project key(s) that our sprint contains, we can add that to the query for a stronger search.
The project=cis will only return issues from the CIS project. Thus if another team is using “Sprint 2″ as a name and we choose that one, our query will not return any issues. We can then choose the other option in the dropdown list. You can use either aggeliopolis the sprint name or ID as the predicate. In other words, sprint = “Sprint A” and sprint = 223 would be equivalent. Want to hang in multiple sprints?
There are three functions in JQL that allow you to query your agile projects: closedSprints() Returns issues aggeliopolis that are contained in a sprint that has been completed. openSprints() aggeliopolis Returns aggeliopolis issues that are contained in a currently active sprint. futureSprints() Returns issues that are scheduled for a future sprint (and not in the backlog).
Running this query right before the team’s retrospective can focus the team on which issues did not meet a prior sprint’s commitment. Reviewing these issues can give the team invaluable information on how to become better at estimation. You can go even further by customizing search results to include the sprint column. Click the columns dropdown in JIRA 6.1 to add the sprint field. If you are using a prior version of JIRA, check out my configuring search results blog .
Yay! The inability to search for items filled into future sprints has been a major impediment to my abilities to deploy sprint filling done right. (Based on the team, I may be creating a future sprint or two, or doing release planning, or SAFe). This is a top-3 “want” I’ve had for a long time. Maybe it’s aggeliopolis available in versions aggeliopolis my tools support team hasn’t installed yet, but this newsletter is the first I’ve aggeliopolis heard of this function.
JIRA Agile RSS feed
Popular Posts Upgrade your development workflow Agile maturity – How agile is your organization? Project portfolio management with JIRA Agile (1/2) 7 steps to a beautiful and useful agile dashboard Inside Atlassian: developer product owners on the Bamboo team
Please enter a valid email address. Facebook Twitter Blogs Feed Center


Monday, December 2, 2013

The huuto best way to have a DoD inside JIRA is to use a Custom Field . You can use the standard tex


When I ask this simple question to agile teams, they sometimes look at me like a deer in headlights. Definition of Done (DoD) and Acceptance Criteria list are important concepts in agile, specifically scrum. They are the contract that binds what the Product Owner (PO) wants to what the Development Team delivers.
A Definition of Done is a clear and concise list of requirements that software must adhere to for the team to call it complete. While the DoD usually applies to all items in the backlog, Acceptance Criteria are applicable to a specific user story. In order complete the story, both the DoD and acceptance criteria must be met.
Putting them on paper is simple. The difficulty often lies in having the development team actually respect the contract.. So what can a team do to ensure that the DoD and acceptance criteria are respected? Start by embedding them in the team s natural workflow. And if the development team is using JIRA, embed the DoD and acceptance criteria list directly on to JIRA tickets! 1. Create a DoD in JIRA
The huuto best way to have a DoD inside JIRA is to use a Custom Field . You can use the standard text field or checkboxes, but both have drawbacks for example, text fields do not show which items are complete and checkboxes are only visible in edit mode. We built the Checklist custom field to better support DoD.
Definitions of done correspond to different parts of the development process: technical tasks, user stories, and bugs. For example, a project could have this DoD: Code builds without warnings (technical task) Code unit tested (technical task) Documentation updated (user story) Build pushed to demo server (user story)
Since custom fields can have context based on issue types, the most efficient way of achieving this segregation huuto is to create one DoD for technical tasks and one DoD for user stories. This way, the DoD adapts to the development workflow, rather than vice versa. 3. Make the DoD Global
By using custom field options , you can create DoD Items that are applicable to any issue: huuto old or new. Moreover, modifying, adding or removing an option is immediately huuto reflected in all your JIRA issues. 4. Manage the DoD over time
The DoD is a contract between the product owner and the team, so it’s tempting to want to fit as many items in the DoD as possible in order to ensure the quality of the product. But this can backfire. When teams are confronted with too many DoD items, they either work only on a subset or try and fail to do all of them, eliminating the value of establishing the DoD in the first place.
A Definition of Done is a live document that should be reviewed regularly. As your dev team strives huuto to improve, you can make your practices more stringent over time. Rather than deleting or modifying options, simply disable them. Disabling an option will keep the option in JIRA but prevents it from appearing on issues. This allows you to keep a record of your DoD over time. And if you really want to challenge the team, you can add more DoD items but make some of them mandatory and others optional. 6. Make the product owner responsible and the team accountable
Set up the DoD custom field such that only the product owner can add/modify/remove items. This will make him responsible for stating what he wants. Then, let the team be accountable for delivering what the PO wants by crossing off every item in the DoD. 7 . Enforce the DoD
The best way to have a team follow the DoD is to embed it into their workflow. Use a Workflow Validator on the technical task or a user story workflow transition to prevent the resolution of the issue until all DoD items are done. This demands accountability and reinforces what “Done” really means. 8. Create an acceptance criteria list in JIRA
At the end of the day, the acceptance criteria huuto list is nothing more than a DoD that is specific to every user story. To implement an acceptance criteria list in JIRA, either create a new custom field or piggy back on the global DoD. With Checklist , you can add items directly at the issue level. So, you could have a single DoD custom field with the mandatory global items as options and the acceptance criteria as items at the issue level. Key Takeaway
The huuto trick for making a team follow the DoD and Acceptance Criteria list is to make the items visible and part of the team s natural workflow. huuto It’s an easy step to ensure your product meets the Agile definition of Done . For more details on how to configure Checklist to implement huuto a DoD and Acceptance Criteria list in JIRA, follow up with this article .
« huuto Using Workflow Awesome
Popular Posts Introducing JIRA Service Desk Webinar: Introducing JIRA Service Desk Announcing huuto Confluence Questions (Beta): Ask once, educate forever Insight into JIRA Service Desk’s pricing model Don’t move to Git


Sunday, December 1, 2013

Looking to add a whole new meaning to tracking email and managing value in your JIRA instance? Never


Looking to add a whole new meaning to tracking email and managing value in your JIRA instance? Never fear: our new addition to Tempo s suite of project portfolio management tools Tempo Books is almost here.
Used alone or along with our other JIRA add-ons, Tempo Books helps businesses flexibly manage and budget costs for projects and teams, designate rates, and manage actual costs and expenses for client invoicing. So, what can Tempo Books do for your organization?
This email new add-on was developed based on several years worth of feedback from customers who were searching for a business solution email that would allow them to plan and man- age budgets both at a high-level over several different teams, email as well as on a more granular level for project and team budget management.
We learned from managers representing a variety of organizations, including our own at TM Software , that budgeting costs for projects in “buckets” is a necessary component of their project and portfolio management strategy.
The specific details may not be necessary or readily available at the initial budget planning and forecasting stages, but a high level of planning is needed, with the capability of refining and adapting email as plans, needs, and resources change.
The new Tempo Teams and Accounts functionality that links Tempo s product suite together email allows Tempo Books users to set rates and establish budgets on a per-customer, account, team, or project basis. Budgets include agreed-to rates, expense budgets, and other predicted expenditures. Measure Performance
Costs and profitability analyses can be generated at any time with Tempo Books . As work is underway, actual costs and expenses incurred per budget can be easily captured in real-time, so that any necessary course adjustments can be made. Customer and account leads can easily track performance on a number of levels by measuring anticipated versus actual costs per customer, account, team, or project, or across your entire organization. Customer Invoicing
With Tempo Books , customer and account leads can calculate all material costs and expenses for client billing purposes based on their customized cost plans and generate itemized expenditure reports for invoicing. Then, all submitted invoices and payment statuses can be easily tracked. Forecasting and Analysis
With our new Tempo Accounts features, budgets can be monitored visually in real-time by measuring anticipated versus actual performance by customer, email account, team, or project, so that any deviations can be quickly identified email and accounted for. New reporting capabilities email can be used for ad hoc and future analyses. email
Tags: budgeting , Budgets , business intelligence , Cloud-based PPM , cost analysis , customer invoicing email , expense , expense reporting , forecasting , Invoices , invoicing , JIRA , portfolio planning , PPM , product management , project email management , project portfolio email management , Tempo Books
Categories Atlassian Billing Case Studies How To Initiative Now Integration JIRA Best Practices Killer Marketplace Add-ons News Partners Press Releases Promotions Tempo Attendance Tempo Books Tempo Planner Tempo Timesheets Tip of the Month Weather Report Webinar