Does ".idea/workspace.xml" contain any user-specific settings that would make it problematic to be in version control?

In this related thread here: https://intellij-support.jetbrains.com/hc/en-us/community/posts/206265629-Do-you-check-your-idea-directories-and-iml-files-into-source-control-?input_string=Do%20people%20typically%20check%20their%20%22.idea%2Fworkspace.xml%22%20into%20the%20version%20control%3F 

people mention that it's usually annoying when people check in `.idea/*` into their source code repository. This is because they often times contain specific developer settings that you do not want to share with others. And then when checking in, your`.idea/*` directory will always show up dirty. Thus why people put it on their ignore list like .gitignore to exclude it. 

But in our Gradle java project, ".idea/workspace.xml" has a very important feature:

<system id="GRADLE">
  <state>
    <task path="$PROJECT_DIR$/my-project/web-service-stubs">
      <activation>
        <before_compile>
          <task name="build" />
        </before_compile>
        <before_rebuild>
          <task name="build" />
        </before_rebuild>
      </activation>
    </task>

This gradle task builds the web service stubs needed to Build the project. But without ".idea/workspace.xml" checked in, this means that you won't get this important change and your Build project will fail until manually making this change. 

How often is workspace.xml dirtied from normal development? Is checking this file in going to become an annoying nuisance?