Automation for JIRA #001 - "re-fetch"

Today I'm going to describe how to edit data with "re-fetch" action in the issue fields in Jira.
About Jira and it's automation I will write much more other day. Now just a few words to introduce.

"Automation for Jira helps you extend and automate Jira - without the need for scripts. Think of it as Lego. You simply put the building blocks together and automate the processes you need easily."
The above quote is coming from the official Automation for Jira site. In my opinion the automation is not as simple as lego but yes it is very helpful and you can automate your processes with blocks building.

Alright let's move to the main topic for today. The issue was to prepare the automation rule for such thing: [When a new servicedesk inquiry is sent (issue is created) clone a task to other project with a "working title" (smart value) which should be copied from the servicedesk "summary".]

The main reason why I'm writing about this is that there is not way to do that without a one specific action.
Please analyze screen shots below:

When labels conditions are met this automation will edit an issue field and copy the summary to "working title". After that when an another labels conditions are met clone the task to the other project with the "working title" in it.

Looks simple but the above automation will not be possible without the action named "re-fetch".
Without it, automation will not copy the "working title" smart value and it will not be present in the cloned task.

The official definition of the "Re-fetch" issue data:
This action refreshes smart values with the latest field values. By default the {{issue}} reference is not updated during a rule execution, and therefore contains the same values as when the rule originally triggered.

It took me some time to figure it out why this automation did not copy this smart value named "working title". When I discovered it I wanted to shout it out.

Until next time, keep it up!

source: docs.automationforjira.com

ITIL - Service Strategy Management

Foreword
What is ITIL? ITIL (IT Infrastructure Library) describes best practices for the effective and efficient provision of IT services.
That is the shortest definition of ITIL I could found. Today I study a service strategy management. This is the first stop of this complex management system.

Service Strategy determines which types of services should be offered to which customers or markets.
The ITIL service lifecycle stage of Service Strategy includes the following main processes:

Strategy Management for IT Services
Process Objective: To assess the service provider's offerings, capabilities, perspective, patterns and competitors as well as current and potential market spaces in order to develop a strategy to serve customers. Once the strategy has been defined, Strategy Management for IT Services is also responsible for ensuring the implementation of the strategy.

Service Portfolio Management
Process Objective: To manage the service portfolio. Service Portfolio Management ensures that the service provider has the right mix of services to meet required business outcomes at an appropriate level of investment.

Financial Management for IT Services
Process Objective: To manage the service provider's budgeting, accounting and charging requirements.

Demand Management
Process Objective: To understand, anticipate and influence customer demand for services. Demand Management works with Capacity Management to ensure that the service provider has sufficient capacity to meet the required demand.

Business Relationship Management
Process Objective: To maintain a positive relationship with customers. Business Relationship Management identifies the needs of existing and potential customers and ensures that appropriate services are developed to meet those needs.

source: wiki.en.it-processmaps.com, flycastpartners.com/itil-service-lifecycle-guide/

The beginning...

"Hello world!"
Today is a first day of this newly created blog. I am stalkerowaty and I will write down here my experience with my work and everyday life. The blog will be a "job" notebook of new terms, interesting issues and things related to IT.
I will write everything in english (I am sorry for the langauge mistakes in advance).